StackBlitz Webcontainer: Prisma fails in multiple ways

Prisma can be installed in the new StackBlitz Webcontainers with a small workaround of installing a Chrome extension that disables CORS: https://github.com/prisma/prisma/issues/7185#issuecomment-845477829
Then you can:

Go to https://stackblitz.com/edit/node-psqsqe
In the terminal run npm install -D prisma@dev
Run npx prisma init
Or run npx prisma

But other commands fail in different ways:
npx prisma studio
In terminal: Unimplemented channel, ignoring request: {}
In browser console:
vendor.js:59 Unable to communicate with backend:  SyntaxError: Unexpected token  in JSON at position 0
    at JSON.parse (<anonymous>)
    at browser.js:1
    at browser.js:1

Internal discussion: https://prisma-company.slack.com/archives/CC8F34ALF/p1621545670013400
npx prisma format
/projects/node-psqsqe
❯ npx prisma format
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Command failed with exit code 1<EMAIL_ADDRESS>format -i /projects/node-psqsqe/prisma/schema.prisma
SyntaxError: Invalid or unexpected token
    at __global_eval__ (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:8:15954)
    at _0x18a892 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:21075)
    at _0x372288.runInThisContext (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:20268)
    at _0x2e8059 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:19362)
    at wrapSafe (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:186554)
    at Module._compile (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187186)
    at Object.Module._extensions..js (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187908)
    at Module.load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:185988)
    at Function.Module._load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:183564)
    at Function.executeUserEntryPoint [as runMain] (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:794701)

error Command failed with exit code 1

npx prisma generate / npx prisma migrate dev / npx prisma db push
/projects/node-psqsqe
❯ npx prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Get config SyntaxError: Invalid or unexpected token
    at __global_eval__ (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:8:15954)
    at _0x18a892 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:21075)
    at _0x372288.runInThisContext (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:20268)
    at _0x2e8059 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:19362)
    at wrapSafe (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:186554)
    at Module._compile (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187186)
    at Object.Module._extensions..js (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187908)
    at Module.load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:185988)
    at Function.Module._load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:183564)
    at Function.executeUserEntryPoint [as runMain] (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:794701)

error Command failed with exit code 1

npx prisma introspect
/projects/node-psqsqe
❯ npx prisma introspect
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma

Introspecting based on datasource defined in prisma/schema.prisma …
Error: Error in introspection engine: SyntaxError: Invalid or unexpected token
    at __global_eval__ (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:8:15954)
    at _0x18a892 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:21075)
    at _0x372288.runInThisContext (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:20268)
    at _0x2e8059 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:19362)
    at wrapSafe (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:186554)
    at Module._compile (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187186)
    at Object.Module._extensions..js (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187908)
    at Module.load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:185988)
    at Function.Module._load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:183564)
    at Function.executeUserEntryPoint [as runMain] (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:794701)

error Command failed with exit code 1

npx prisma -v
/projects/node-psqsqe 8s
❯ npx prisma -v
Environment variables loaded from .env
Error: Command failed with exit code 1<EMAIL_ADDRESS>--version
SyntaxError: Invalid or unexpected token
    at __global_eval__ (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:8:15954)
    at _0x18a892 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:21075)
    at _0x372288.runInThisContext (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:20268)
    at _0x2e8059 (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:11:19362)
    at wrapSafe (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:186554)
    at Module._compile (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187186)
    at Object.Module._extensions..js (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:187908)
    at Module.load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:185988)
    at Function.Module._load (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:183564)
    at Function.executeUserEntryPoint [as runMain] (https://node-psqsqe.jw.staticblitz.com/blitz.7286dbe8d47d3473cde7be488b7d048fb59b05f2.js:6:794701

Probably a problem on the StackBlitz side, reported at https://github.com/stackblitz/webcontainer-core/issues/16

Confirmed: New StackBlitz can not run any binaries, only WASM stuff :(

With https://github.com/prisma/prisma/issues/8626#issuecomment-1426853638 we are now fully Wasm in the Prisma CLI, so some of the commands actually work (as long as you have a CORS-enabling extension installed, I used this one this time: https://chrome.google.com/webstore/detail/cors-unblock/lfhmikememgdcahcdlaciloancbhjino). You can prisma init and then successfully prisma generate a Prisma Client. You can still not use any command that uses the Migration Engine, and Prisam Client itself can also not be used.
Will continue watching the topic via https://github.com/prisma/prisma/issues/8626. Slow and strady.


Automatic dependency collection for @azure/arm- SDKs

Package Name: @azure/arm-
Package Version:"@azure/arm-keyvault": "2.0.0",
"@azure/arm-network": "30.1.0",
"@azure/arm-resources": "5.1.0",

Operating system:
[x] nodejs

version: 16LTS & 18LTS

[x] typescript

version: 4.9.4

Describe the bug
I'm struggling to enable automatic log collection for @azure/arm SDKs. Currently, I'm using @azure/arm-keyvault, @azure/arm-network and @azure/arm-resources. Is there some extra configuration needed? @microsoft/microsoft-graph-client, @azure/cosmos and lots of other dependency logs are collected flawlessly.
Expected behavior
I thought logs are collected automatically. If not, please guide me to working, uptodate documentation.
Screenshots
In this screenshot one can see the missing dependency logs. The health requests takes 3 second and there are no correlated logs for the last 2 seconds, when arm SDKs are making requests. The logs are missing in the transactions list as well.

Additional context
I already tried to get help here:

https://github.com/microsoft/ApplicationInsights-node.js/issues/1055
https://stackoverflow.com/questions/75108835/automatic-application-insights-dependency-collection-for-azure-arm-sdks

appInsights
  .setup(configService.get("APPLICATIONINSIGHTS_CONNECTION_STRING"))
  .setDistributedTracingMode(DistributedTracingModes.AI_AND_W3C)
  .setAutoCollectConsole(false, false)
  .setAutoCollectExceptions(true)
  .setAutoCollectPerformance(true, true)
  .setAutoCollectPreAggregatedMetrics(true)
  .setAutoCollectHeartbeat(true)
  .setAutoCollectRequests(true)
  .setAutoCollectDependencies(true)
  .setAutoDependencyCorrelation(true)
  .setUseDiskRetryCaching(true)
  .setInternalLogging(false, true)
  .setSendLiveMetrics(true)
  .start();

It’s nice

checking, will provide more infomation when I have any progress.

@DaniSchenk Could you show me how to get the screenshot like that ? Is the log coming from the console log or from network    ? Also, Could you help explain more about the code snippet you shared ? and how do I create an appInsights like that ? Thank you

Hey @qiaozha

Could you show me how to get the screenshot like that ?

The screenshot was taken from the azure portal. I navigated to my Application Insights instance → Transaction search and picked one log of event type Request.

Is the log coming from the console log or from network ?

I have a node application running and integrated the application-insights SDK for node. This SDK automatically collects and correlates the logs shown in the screenshot. The request log is the very first line in the screenshot and the request takes about three seconds. All log lines below are dependency logs (CosmosDB, Graph API) automatically collected and correlated. But you can see, that there are missing logs from the last two seconds of this request. In these last 2 second, I'm using multiple @azure/arm- SDKs. I expected that requests made by these SDKs to show up as dependency logs as well.

Also, Could you help explain more about the code snippet you shared ?

This code snippet shows my current application insights SDK configuration/setup, that is working for all events (requests/dependencies/exceptions) except @azure/arm- SDKs

how do I create an appInsights like that ?

There are lots of tutorials out there by Microsoft how to set up Application Insights for node. My setup is basic, and my configuration is shown in the code snippet.
The most important question to me is:
Can I expect @azure/arm- SDKs usage to be automatically collected and correlated by the AI SDKs?

Thanks for providing these details. it's very helpful.

@DaniSchenk I'd like to confirm the details with you, the question is - we expect to collect all requests/responses for arm- SDKs but currently we can't collect any of these info, Right?

Adding the Service team to provide the pointers.
@jennyhunter-msft @josephkwchan Could you please let us know the right service team that can assist on this ?


Add X-Frame-Options

Overview
Adds X-Frame-Options support to help protect against clickjacking.
X-Frame-Options is configurable via the config and allows for DENY,
SAMEORIGIN and ALLOW-FROM. See Mozilla Docs for a nice introduction to it.
Testing recommendations

Checklist

[x] Code is written and works correctly;
[x] Changes are covered by tests;
[ ] Documentation reflects the changes;

@tonysun83 thanks for the review. I've made all the fixes you recommended

+1 after squash


Update @lezer/common and @lezer/lr

I'm working on a project that utilizes both the CodeMirror editor and Parcel. Since both CodeMirror and Parcel utilize the lezer parser system, Parcel's older version of @lezer/common is conflicting with the current version of @lezer/common that I need for my project. Any help is appreciated, thanks!

@mischnic what do you think about upgrading to ^1.0.0 of both @lezer/common and @lezer/lr and then releasing as a patch version?
This would allow people with existing transitive dependencies to upgrade without other depending packages having to release new versions...

@mischnic To be clear about the problem, if other packages such as CodeMirror use modern versions of @lezer/common and @lezer/lr, then things like syntax highlighting will break, which can easily make it to production without someone noticing:

https://github.com/uiwjs/react-codemirror/issues/216
https://github.com/codemirror/dev/issues/666

There are workarounds with Yarn Resolutions or npm/pnpm Overrides mentioned in the issues above, but it would be great if @mischnic/json-sourcemap used a modern version of @lezer/common and @lezer/lr out of the box.

I'll try to do this soon. Last time I tried I ran into some problems when upgrading https://github.com/mischnic/parcel-transformer-lezer (used here to build the package) to use the 1.0.0 version lezer

0.1.1 is published, let's hope I didn't break anything.


Add warning when SVG with foreign object is included

A bit unfortunate to have to search every SVG like this (I'm also not sure if this might be very unefficient, if so I'm open for suggestions on how to improve it), but I think it's good to have a warning, so we can finally close #1421 since there isn't much we can do from our side.
I tested it manually to confirm that it works.

Thank you!


Close Jira Issue does not working when closing a finding

Hi. I found that we're unable to close the finding ticket in Jira (Cloud Jira).
before we're using v2.20.1 and it still works and after updating to v2.26.3 it suddenly not sending the comment and the jira status update
here are the logs
[26/Sep/2023 10:04:41] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[b3fbdbdc-a880-43f7-879b-8cc64aee593e] succeeded in 0.004412852227687836s: None
[26/Sep/2023 10:05:06] INFO [celery.worker.strategy:161] Task dojo.utils.close_external_issue[9be5ba73-3249-4e61-9012-6e3c847c644a] received
[26/Sep/2023 10:05:06] INFO [celery.app.trace:131] Task dojo.utils.close_external_issue[9be5ba73-3249-4e61-9012-6e3c847c644a] succeeded in 0.012584502808749676s: None
[26/Sep/2023 10:05:06] INFO [celery.worker.strategy:161] Task dojo.finding.helper.post_process_finding_save[9aa69e59-c3ea-4791-a477-a8cff8db3010] received
[26/Sep/2023 10:05:06] INFO [celery.app.trace:131] Task dojo.finding.helper.post_process_finding_save[9aa69e59-c3ea-4791-a477-a8cff8db3010] succeeded in 0.009278942830860615s: None
[26/Sep/2023 10:05:06] INFO [celery.worker.strategy:161] Task dojo.notifications.helper.send_msteams_notification[8022a649-8011-405c-85f0-9748611d648a] received
[26/Sep/2023 10:05:10] INFO [celery.app.trace:131] Task dojo.notifications.helper.send_msteams_notification[8022a649-8011-405c-85f0-9748611d648a] succeeded in 3.921074328944087s: None
[26/Sep/2023 10:05:10] INFO [celery.worker.strategy:161] Task dojo.notifications.helper.send_msteams_notification[47afd1be-6479-44d1-9b2c-af5be70e6df6] received
[26/Sep/2023 10:05:10] INFO [celery.app.trace:131] Task dojo.notifications.helper.send_msteams_notification[47afd1be-6479-44d1-9b2c-af5be70e6df6] succeeded in 0.00036281393840909004s: None
[26/Sep/2023 10:05:41] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[5cc64763-b22b-4f5b-ac3d-36ebc3de8fd4] received
[26/Sep/2023 10:05:41] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[5cc64763-b22b-4f5b-ac3d-36ebc3de8fd4] succeeded in 0.00437155831605196s: None
when I compare it to our local defectdojo that sent a close request to Jira local (not cloud) it is working normally with below logs
[26/Sep/2023 09:36:09] INFO [celery.app.trace:131] Task dojo.tasks.async_dupe_delete[089bb446-a2fe-4fea-9fc7-d7ca9f10f87d] succeeded in 0.006762905046343803s: None
[26/Sep/2023 09:36:21] INFO [celery.worker.strategy:161] Task dojo.utils.close_external_issue[97dbf75b-5172-4b65-a235-ec9e9527780f] received
[26/Sep/2023 09:36:21] INFO [celery.app.trace:131] Task dojo.utils.close_external_issue[97dbf75b-5172-4b65-a235-ec9e9527780f] succeeded in 0.020419767126441002s: None
[26/Sep/2023 09:36:21] INFO [celery.worker.strategy:161] Task dojo.jira_link.helper.add_comment[a62d44fb-575c-4ebf-926f-a3f64a5c0aae] received
[26/Sep/2023 09:36:22] INFO [celery.app.trace:131] Task dojo.jira_link.helper.add_comment[a62d44fb-575c-4ebf-926f-a3f64a5c0aae] succeeded in 0.4849044680595398s: True
[26/Sep/2023 09:36:22] INFO [celery.worker.strategy:161] Task dojo.finding.helper.post_process_finding_save[803e0402-b4a1-4454-99a1-63ce986b788b] received
[26/Sep/2023 09:36:22] INFO [celery.app.trace:131] Task dojo.finding.helper.post_process_finding_save[803e0402-b4a1-4454-99a1-63ce986b788b] succeeded in 0.04339374788105488s: None
[26/Sep/2023 09:36:22] INFO [celery.worker.strategy:161] Task dojo.jira_link.helper.update_jira_issue_for_finding[a9cfb261-8776-4435-9d78-8f9d1cf7c9b3] received
[26/Sep/2023 09:36:22] INFO [celery.app.trace:131] Task dojo.jira_link.helper.update_jira_issue_for_finding[a9cfb261-8776-4435-9d78-8f9d1cf7c9b3] succeeded in 0.6336308941245079s: True
[26/Sep/2023 09:36:22] INFO [celery.worker.strategy:161] Task dojo.finding.helper.post_process_finding_save[d4190d54-899b-469a-8964-875577ba4b2b] received
[26/Sep/2023 09:36:22] INFO [celery.app.trace:131] Task dojo.finding.helper.post_process_finding_save[d4190d54-899b-469a-8964-875577ba4b2b] succeeded in 0.02380809187889099s: None
[26/Sep/2023 09:37:09] INFO [celery.worker.strategy:161] Task dojo.tasks.async_dupe_delete[9d3d79fd-c1a5-4323-8771-d97fbb941591] received
as you can see, some tasks did not run such as add_comment and update_jira_issue_for_finding.
anyone have some thougt about this?
Steps to reproduce
Steps to reproduce the behavior:

configure jira integration
view finding that already have jira issue linked
close the finding and fill the notes/comment
close finding
result (did not close the jira ticket)

Expected behavior
wanted to know why is this possible, and possibility to fix this issue
Deployment method (select with an X)

[X] Docker Compose
[ ] Kubernetes
[ ] GoDojo

Environment information

Operating System: CentOS 7
DefectDojo version : v2.26.3

Logs
Use docker-compose logs (or similar, depending on your deployment method) to get the logs and add the relevant sections here showing the error occurring (if applicable).
Sample scan files
If applicable, add sample scan files to help reproduce your problem.
Screenshots
Production Dojo pushing to Jira Cloud

Local Dojo pushing to local jira

Additional context (optional)
Add any other context about the problem here.

add note:
as you can see, some tasks did not run such as add_comment and update_jira_issue_for_finding.
Does anyone have some thoughts about this?


fix(env_mnemonic): dont prompt for save if the given mnemonic is on env

Description of change
If the user passes the mnemonic that's already saved on the env to the account initialiser, ignore the prompt with info since it's already managed by the user.
Type of change

Bug fix (a non-breaking change which fixes an issue)

How the change has been tested
The faucet uses the wallet library this way so it's a way to test it (it always passes the mnemonic to the account creation and it already saves it to it's own .env)
Change checklist

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have checked that new and existing unit tests pass locally with my changes

Might this be an attack vector if the attacker can set the ENV?

Maybe better to also hide this behind a buildtime feature?

yeah tbh this feature is only meant to be provisory to get the testnet up and running; I think we should rethink this later or maybe force stronghold usage.

@lucasfernog - maybe add a TODO


chore: port in url handling improvements

Explicitly specifying port in p2p url should not be neccessary (just a room for mistakes).
Also - SafeUrl should reject any URLs for which we don't know which port to use as early as possible, to limit room for mistakes.

Successfully created backport PR for releases/v0.3:

#5349


TLS 1.0 connection issues

Hi Team,
I am performing testing using NetX Duo v6.2.0 and am running into behavior I am not understanding when trying to use TLS 1.0 connections both as a server and as a client.
Client connection issues
I have a python script running on a RPi as a server. The script is forcing use of TLS 1.0 by using ssl_version=ssl.PROTOCOL_TLSv1 in the wrap socket call.
In my NetX Duo code, I am establishing the TLS connection to the RPi. If I use the protocol version override API to force the client to use TLS 1.0 by calling
error = nx_secure_tls_session_protocol_version_override(&tls_session, NX_SECURE_TLS_VERSION_TLS_1_0);
then the connection is successfully established.
If I remove the call to nx_secure_tls_session_protocol_version_override then the connection fails. nx_secure_tls_session_start returns an error code of NX_SECURE_TLS_ALERT_RECEIVED (0x114) and the python script displays the error:
('(accept) ERROR: ', SSLError(1, '[SSL: NO_SHARED_CIPHER] no shared cipher (_ssl.c:1056)'))
Everything is exactly the same on both sides except for the call to nx_secure_tls_session_protocol_version_override. Why the difference in behavior?
Server connection issues
For the server connection test, on the RPi I am using the program ssl_client2 from the mbedTLS distribution. Using the command:
./ssl_client2 server_addr=$1 ca_file=ec-cacert.pem crt_file=device-cert.pem key_file=device-key.pem server_name="NJSASC" server_port=50007 debug_level=1
The connection to my NetX Duo test program succeeds. But if I force using TLS 1.0 using the command
./ssl_client2 server_addr=$1 ca_file=ec-cacert.pem crt_file=device-cert.pem key_file=device-key.pem force_version=tls1 server_name="NJSASC" server_port=50007 debug_level=1
then the connection fails. If I use the call to nx_secure_tls_session_protocol_version_override then the error returned from nx_secure_tls_session_start is NX_SECURE_TLS_CERTIFICATE_VERIFY_FAILURE (0x131). If I remove the call to version_override than the error returned is NX_SECURE_TLS_NO_SUPPORTED_CIPHERS (0x10e).
I don't understand the difference in behavior I'm seeing. The different results seem like a bug to me. The certificates used are the same in every test case for both client and server test cases.
Environment
NetX Duo: v6.2.0
RPi: Linux raspberrypi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux
mbedTLS: 2.25.0 - programs/ssl/ssl_client2
Python3: 3.7.3
OpenSSL: 1.1.1n  15 Mar 2022
I had to modify the OpenSSL config for TLS 1.0 to work:
[system_default_sect]
MinProtocol = TLSv1.0
CipherString = DEFAULT@SECLEVEL=1
GCC: 10.3.1
In nx_secure_user.h I have:
#define NX_SECURE_TLS_ENABLE_TLS_1_0
#define NX_SECURE_TLS_ENABLE_TLS_1_1
#define NX_SECURE_TLS_ENABLE_TLS_1_3
and in nx_crypto_ciphersuite_lookup_table_ecc[] I added
/* Added for TLS1.0 testing */
{TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,    &crypto_method_ecdhe,     &crypto_method_ecdsa,     &crypto_method_aes_cbc_256,     16,      32,        &crypto_method_hmac_sha1,       20,        &crypto_method_tls_prf_sha256},
If you can help me understand the behavior, I would greatly appreciate it.
Thanks,
Doug

I have determined that the client connection issue is a problem with my code. Investigating more I found out that the ciphersuites that the code was using was being set differently when the nx_secure_tls_session_protocol_version_override() was being used. If the override call wasn't being used, the TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA cipher wasn't being added. Fixing that fixed the client connection issue.
But I am still seeing a problem with the server connection. If the remote client forces TLS1.0 then the NetXSecure code is failing the certificate verification. If the remote client does not force TLS 1.0 then a TLS 1.2 connection is established using the same certificate.
Remote client command for successful connection:
./ssl_client2 server_addr=$1 ca_file=ec-cacert.pem crt_file=device-cert.pem key_file=device-key.pem server_name="NJSASC" server_port=50007 debug_level=1
Connection succeeds using the TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 cipher.
Remote client command for failed connection:
./ssl_client2 server_addr=$1 ca_file=ec-cacert.pem crt_file=device-cert.pem key_file=device-key.pem force_version=tls1 server_name="NJSASC" server_port=50007 debug_level=1
Connection fails using the TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA cipher. The certificate check is failing in _nx_crypto_method_ecdsa_operation().
How can I determine why the same certificate works with one cipher but not the other?

Did a little more digging into this today. When using TLS 1.0, the verification of the signature of the hash data is failing in _nx_crypto_ecdsa_verify. I've included some of the debug statements I've added in my environment. Limited use to you but it does show the cipher being choosen for the connection.
The entry in the ciphersuite table for TLS 1.0:
{TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,    &crypto_method_ecdhe,     &crypto_method_ecdsa,     &crypto_method_aes_cbc_256,     16,      32,        &crypto_method_hmac_sha1,       20,        &crypto_method_tls_prf_sha256},
Happy to run any tests that would be helpful. At this point I don't know what to do to figure out why the verification is failing.
Successful server test using TLS 1.3.
Test TLS server mode
======TLS server test===========
======TLS server waiting for client connection===========
======Client connected===========
TLS session created
Assigning protocol_version #1 to 0x303 (1)
Found ciphersuite match: 0x1301
...saving ciphersuite: 0x1301, priority: 0
*********Found acceptable ciphersuite: 0x1301
Assigning protocol_version #1 to 0x303 (1)
Found ciphersuite match: 0x1301
...saving ciphersuite: 0x1301, priority: 0
*********Found acceptable ciphersuite: 0x1301
Found certificate method - index 0, method 0x80024a8
_nx_crypto_method_ecdsa_operation: op 41
_nx_crypto_method_ecdsa_operation: op 3
Found certificate method - index 0, method 0x80024a8
_nx_crypto_method_ecdsa_operation: op 41
_nx_crypto_method_ecdsa_operation: op 4
NX_CRYPTO_VERIFY #1
_nx_crypto_ecdsa_verify: curve 0x100438e0, hash_length 32
3694fbcf74aae9aa713722f6ade9bbd0a95907eb2756ddea683a0a2800dd47df
verify: compare IS successful
status of verify: 0x00
_nx_secure_tls_process_certificate_verify: tls version 0x0303 (1)
Found certificate method - index 0, method 0x80024a8
_nx_crypto_method_ecdsa_operation: op 41
Calling nx_crypto_operation: 0x1001dd85
_nx_crypto_method_ecdsa_operation: op 4
NX_CRYPTO_VERIFY #1
_nx_crypto_ecdsa_verify: curve 0x100438e0, hash_length 32
1d2f41b28a34ab485f4db73aa125d7ee8ba6466fc7350578ca0ec0751149b191
verify: compare IS successful
status of verify: 0x00
SUCCESS compare_value: 0
--Connection successful
Failed server test with client specifying TLS 1.0
Test TLS server mode with client specifying TLS1.0
======TLS server test===========
======TLS server waiting for client connection===========
======Client connected===========
TLS session created
Assigning protocol_version #1 to 0x301 (1)
Assigning protocol_version #1 to 0x301 (0)
Found ciphersuite match: 0xc00a
...saving ciphersuite: 0xc00a, priority: 12
*********Found acceptable ciphersuite: 0xc00a
Found certificate method - index 7, method 0x80024fc
_nx_crypto_method_ecdsa_operation: op 41
_nx_crypto_method_ecdsa_operation: op 3
Found certificate method - index 0, method 0x80024a8
_nx_crypto_method_ecdsa_operation: op 41
_nx_crypto_method_ecdsa_operation: op 4
NX_CRYPTO_VERIFY #1
_nx_crypto_ecdsa_verify: curve 0x100438e0, hash_length 32
3694fbcf74aae9aa713722f6ade9bbd0a95907eb2756ddea683a0a2800dd47df
verify: compare IS successful
status of verify: 0x00
_nx_secure_tls_process_certificate_verify: tls version 0x0301 (0)
Found certificate method - index 0, method 0x80024a8
-----MD5 hash method: 0x80029b0 (crypto_method_md5)
-----SHA1 hash method: 0x8002a10 (crypto_method_sha1)
_nx_crypto_method_ecdsa_operation: op 41
Calling nx_crypto_operation: 0x1001dd85
_nx_crypto_method_ecdsa_operation: op 4
NX_CRYPTO_VERIFY #1
_nx_crypto_ecdsa_verify: curve 0x100438e0, hash_length 36
08029ea6ab3c2c119bba51c30475dabec3e8c44f7567cfa970c4b7ed5460b7f8dd4fcb55
verify: compare not success
status of verify: 0x20009
NOT SUCCESS compare_value: 1
nx_secure_tls_session_start failed 131

Description:
The TLS 1.1/1.0 handshake fails certificate verify (when using auth_mode=required using mbedtls server/client)
The issue is because for EC cipher suites the handshake verify hash is of size 20 bytes while the netxsecure code is sending MD5 + SHA1 (36bytes) of hash causing failure.
With tls_10_tls_11.patch the issue is resolved.
tls_10_tls_11.patch


Later breaks in certain situations

Later doesn't work when a method is called on a column before other operations.
In : diamonds >> mutate(foo=X.x.mean() + X.x) >> head() >> select(X.x, X.foo)
"""
Out:
      x             foo
0  3.95  NotImplemented
1  3.89  NotImplemented
2  4.05  NotImplemented
3  4.20  NotImplemented
4  4.34  NotImplemented
"""

It works in many other cases though, notably,
In : diamonds >> mutate(foo=X.x + X.x.mean()) >> head() >> select(X.x, X.foo)
"""
Out:
      x        foo
0  3.95   9.681157
1  3.89   9.621157
2  4.05   9.781157
3  4.20   9.931157
4  4.34  10.071157
"""

In [84]: diamonds >> mutate(foo=X.x.mean()) >> head() >> select(X.x, X.foo)
"""
Out[84]:
      x       foo
0  3.95  5.731157
1  3.89  5.731157
2  4.05  5.731157
3  4.20  5.731157
4  4.34  5.731157
"""

In [85]: diamonds >> mutate(foo=X.x.mean() + 1) >> head() >> select(X.x, X.foo)
"""
Out[85]:
      x       foo
0  3.95  6.731157
1  3.89  6.731157
2  4.05  6.731157
3  4.20  6.731157
4  4.34  6.731157
"""

In : diamonds >> mutate(foo=X.x + X.x.mean() + X.x) >> head() >> select(X.x, X.foo)
"""
Out:
      x        foo
0  3.95  13.631157
1  3.89  13.511157
2  4.05  13.831157
3  4.20  14.131157
4  4.34  14.411157
"""

Fixed in #20


chore: Redesign release workflow

Why

We want to move our development process to GitHub Flow
Currently, our release pipeline is built for Git flow.

What

I redesigned the release workflow.

Creation of GitHub Releases can now be done from workflow_dispatch.

Ref

https://github.com/nodecross/nodecross/issues/19

@rabe1028
Thank you!
I have made a few comments, please check them out.

@rabe1028
I'd like to see some documentation added to the README or something on how to release it.

@rabe1028
[CONFIRMATION].
https://github.com/nodecross/nodex/blob/develop/.github/workflows/release-pipeline.yml
Do you need to remove the ?
If you are going to remove it,
If so, please change the release-pipeline badge in the README to release.

@miseyu
Thanks. I removed it and changed the badge in README.


docs: Update README.md for SLSA v1.0

Update docs for SLSA v1.0
Fixes #2007.

Hmm, pre-submits are failing at generate-builder with this error but not sure why.
git: pathspec 'refs/pull/2006/merge' did not match any file(s) known to git

pre-submits are blocked on #2009


Typo in lang file en.json

Hey, thank you for making this system for foundry. We found a typo while playing but were able to modify the json file and fix it, wanted to give a heads up.
under lang/en.json, line 10 there's a typo for Alertness, the display value is "Alerness"
10 >     "DG.Skills.alertness": "Alterness",
Should be changed to "Alertness"

Thanks, I'll get that fixed

Just released version 0.9.7 which should have this fix in it.


selecting filters in genome list shouldn't clear selection

Say you are creating a genome group and pick a few genomes in the genome list, then click "complete" to shift to complete genomes only. If you had genomes selected that remain in the list after the filter is enabled, the genomes are deselected. They should remain selected after the filter is added.

currently filtering triggers a new scoping, which means, all the numbers in the facets are updated and entire grid is also re-populated. So, we cannot keep the selections.

This may lead to confusion. When user changes selection / filters, we can not anticipate whether user wanted to keep the previous selection or not. If we keep it in memory, user has no way to unselect it, without first saving the group.
You can incrementally add genomes to the same genome group using different filters. It may require few more clicks and saves, but I believe it is much cleaner and less confusing mechanism.
Closing the ticket with won't fix as I don't think this is critical issue.


UX Copy: Remove "Event" from UX

We've received feedback that there is confusion about both using the word trigger AND event.
We'll be updating the 'create trigger' flow to avoid the word 'event' in the UX.
We should do a pass through the UX Copy to remove the others.

@mareekuh are we doing anything here for R9?
Dropping myself from assignee since I'm not actively working on this.

(approved) design is here: https://www.figma.com/file/LlTlh5vXwq91zjGnFtrUUR6l/Composer-master-design-spec-%2F-UI-library?node-id=313%3A2806
The labels used in the menu should be the same as the ones in the UI.
Lmk if you have specific q's or when I can check out updates in the build (-:

Do you know if this is done? @vishwacsena s

@sangwoohaan - is this related to the UX terms PR you did the other day?

Please see https://github.com/microsoft/BotFramework-Composer/issues/3175.


Fix JUMP TO

closes #1670
Fixes JUMP TO links and adds ids to methods

Made a PR to your branch with minor enhancements https://github.com/mparke/manager/pull/16


⚠ Shadow Does Streams has degraded performance

In 66a237d, Shadow Does Streams (https://stream.everythingbagel.me) experienced degraded performance:

HTTP code: 200
Response time: 3698 ms

Resolved: Shadow Does Streams performance has improved in 3d258ea after 10 minutes.


interactiveTransactions rollback but don't error out if timeout is reached

Bug description
When using interactive transactions, the transaction returns successfully even if the timeout was reached and internally the transaction was rolled back.
More context here https://github.com/prisma/prisma/issues/8664#issuecomment-930403241
How to reproduce

Clone https://github.com/awinograd/prisma-include-clause-bug/tree/interactive-transaction-timeout (note it is a specific branch, not main branch)
run yarn dev:database
run prisma migrate dev
run yarn dev

Expected behavior
Transaction that surpasses timeout should throw an error rather than returning the return value as if nothing has happened.
Prisma information

all included in repro example above
Environment & setup

OS: MacOS
Database: PostgresQL
Node.js version: 16.9.1

Prisma Version
prisma                  : 3.1.1
@prisma/client          : 3.1.1
Current platform        : darwin
Query Engine (Node-API) : libquery-engine c22652b7e418506fab23052d569b85d3aec4883f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt c22652b7e418506fab23052d569b85d3aec4883f (at node_modules/@prisma/engines/prisma-fmt-darwin)
Default Engines Hash    : c22652b7e418506fab23052d569b85d3aec4883f
Studio                  : 0.423.0
Preview Features        : interactiveTransactions

I can reproduce this. Thanks for the detailed report.

From what I can see on this. The issue is here https://github.com/prisma/prisma/blob/ec0a0182bd81f82b70d1a12a48bd7a523300a5b9/packages/engine-core/src/library/LibraryEngine.ts#L120
The query-engine will never throw an actual error but will return an error object:
{
  "is_panic":false,
  "message":"Transaction API error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired'.",
   "meta":{
        "error":"Transaction already closed: Transaction is no longer valid. Last state: 'Expired'."
    },
 "error_code":"P2028"
}

We need to check the response and throw an error if we detect it. We need to do the same for rollback

PR ready for review: https://github.com/prisma/prisma/pull/10797

I think I've also run into this issue. When I turn on interactiveTransactions preview feature, a long-running transaction invoked the old way (prisma.$transaction([...])) suddenly starts failing with this error:
[0] prisma:info Starting a sqlite pool with 9 connections.
[0] PrismaClientKnownRequestError:
[0] Invalid `prisma_1.prisma.contract.create()` invocation in
[0] /home/livthomas/Projects/livthomas/pawnshop-next/build/main/legacy/contract/importLegacyContractRecords.js:15:41
[0]
[0]   12 const userPasswordsMap = await (0, createUserHashedPasswordsMap_1.createUserHashedPasswordsMap)(userNames);
[0]   13 const operations = results.map(result => {
[0]   14     const data = (0, convertLegacyRecordToContract_1.convertLegacyRecordToContract)(result, userPasswordsMap, archived);
[0] → 15     return prisma_1.prisma.contract.create(
[0]   Transaction API error: Transaction already closed: Transaction is no longer valid. Last state: 'Expired'.
[0]     at Object.request (/home/livthomas/Projects/livthomas/pawnshop-next/node_modules/@prisma/client/runtime/index.js:39054:15)
[0]     at async Promise.all (index 0)
[0]     at async PrismaClient._transactionWithCallback (/home/livthomas/Projects/livthomas/pawnshop-next/node_modules/@prisma/client/runtime/index.js:39655:18)
[0]     at async importLegacyContractRecords (/home/livthomas/Projects/livthomas/pawnshop-next/build/main/legacy/contract/importLegacyContractRecords.js:17:5)
[0]     at async reportLegacyTableImportStatus (/home/livthomas/Projects/livthomas/pawnshop-next/build/main/legacy/reportLegacyTableImportStatus.js:34:9)
[0]     at async importLegacyDatabase (/home/livthomas/Projects/livthomas/pawnshop-next/build/main/legacy/importLegacyDatabase.js:27:20)
[0]     at async electron/js2c/browser_init.js:197:563 {
[0]   code: 'P2028',
[0]   clientVersion: '3.8.0',
[0]   meta: {
[0]     error: "Transaction already closed: Transaction is no longer valid. Last state: 'Expired'."
[0]   }
[0] }

This transaction works without any problems when this preview feature is disabled and its execution usually takes around 30 seconds.
I'm using SQLite database.


Change to main repository

The EDMC infrastructure tests within https://github.com/iofoundry/ontology revealed a number of issues with IOFoundry IRIs, which probably need to addressed even without taking into the considerations the requirements of this infrastructure.
To address these issues I tried to be as minimalistic as possible, but since they concerns identifiers, a diligent review would be recommended.
This pull requests also adds hygiene tests as a GitHub action. These tests are to verify that various requirements as specified in IOF's Confluence page are satisfied. If they prove to hamper ontology development, we may drop them at a later stage.

Are the AboutIOFDev/Prod files supposed to have incorrect IRIs using Perl and YYYYMMDD dates? Is this a test file?

This should be fixed now.

Looks good


build: updating the rhoas guidelines to the newest version

Insert JIRA Issue number and update link
PR owner checklist
Updating the OpenAPI Linter to the newest version in the CI.
Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration.
Run mvn clean verify -DskipTests so that imports are correctly set.
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] The layers in the kustomize folder have been updated accordingly.
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

PR reviewer(s) checklist

[ ] Check if code and Github action workflows have been modified and if the modification is safe
[ ] If the modification is safe, add the safe to test label

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

Deploy BOT
Comment with `/deploy <dev,stable> when the PR has been merged to deploy to a target environment.

@manstis @danielezonca I think we need one more approval, you were first in my mind. Do you have a minute for review this PR please?


Change MIME type of .ico to official one

Proposed changes
The mime type of Nginx has been image/x-icon, which is unofficial and ambiguous.
The official one is image/vnd.microsoft.icon.
There will no one who put other types of icon image files with .ico extension today.
https://stackoverflow.com/questions/1444975/if-i-serve-favicon-ico-as-image-vnd-microsoft-icon-instead-of-image-x-icon-wi

I would like to suggest checking the output of these simple commands:
curl -I https://www.google.com/favicon.ico
curl -I https://github.com/favicon.ico
curl -I https://www.microsoft.com/favicon.ico

In these cases, the headers Content-Type: image/x-icon are used. However, this header can always be configured for any requirements. Therefore, the pull request does not seem relevant.

We need to investigate the current behavior of each browser engine when the x-icon is passed and research how many people put GIF or PNG as favicon.ico first.


Auth support for StatefulSets

Currently Istio Auth does not work for StatefulSets, like those used for databases like Cassandra or Mysql. If injection is enabled cluster-wide, the pods backing the StatefulSet are injected with Envoy, but, if auth enabled, connectivity to them is lost. Example:
INFO  [HANDSHAKE-cassandra-0.cassandra/<IP_ADDRESS>] 2017-10-26 15:14:41,318 OutboundTcpConnection.java:560 - Handshaking version with cassandra-0.cassandra/<IP_ADDRESS>]
StatefulSet services are represented as headless services with selectors, and Istio only implemented TCP passthrough for headless services, which does not work with auth. I am missing the history on this @rshriram , but it would be nice if we could enable the use-case for securing databases with istio, and handle Endpoints that are the result of a StatefulSet.
A workaround for the future would be to disable auth for the headless services, but maybe we can do better.
cc @kyessenov @wattli @linsun

Pilot uses Original Destination feature of Envoy https://www.envoyproxy.io/envoy/intro/arch_overview/service_discovery.html
but it does not add SSL context with SAN.

Currently the auth team is working on a solution for per-service auth enablement. We will let customers play with it and see if there is a strong desire to use auth for this case. And if the answer is positive, we will plan proper resource on it, probably in Q1.

@diemtvu who is working on per-service auth enablement

There integration in pilot in headless.go skip the auth case, they can be changed to use a StatefulSet instead of a Deployment. Same is applicable to bookinfo-mysql in e2e.

you cannot use auth with headless services because access are made to the pods, not to the service. so, identifying the backing service is not feasible. Anything that uses orig dst service cannot use auth. Handling headless services was a special case for us. If we enforce auth, then we have to keep track of the state of a stateful set/cluster, create a listener for every destination pod as applications access pods directly using pod IP (not service IP), add/remove such listeners as pods come up and go, and so on. With 100 pods in the stateful set, there will be 100 listeners in every pod.

FYI, this PR update the headless.go test. It shows the status quo that headless service doesnot work with auth, and per-service annotation can be used to disable it (agree it's not the ideal solution but at least it's a work around for now).

First, I do not have a strong use-case, yet, to justify the need for using auth with StatefulSet, so if anybody has this, please comment on this issue.
You can identify the backing endpoints individually by $(statefulset name)-$(ordinal).$(service name).$(namespace).svc.cluster.local, so it is feasable. I am not so sure we would run into scale problems in a realistic deployment, this is a subset of headless services that is useful for databases, so I expect there will not be a 100 pods.
In any case, how come it works for the non-auth case? Does it match any rule in Envoy? Or is it because it falls into a processing more where anything not matching Envoy is sent to original destination?

On Tue, Oct 31, 2017 at 11:35 AM Andra Cismaru<EMAIL_ADDRESS>wrote:

In any case, how come it works for the non-auth case? Does it match any
rule in Envoy? Or is it because it falls into a processing more where
anything not matching Envoy is sent to original destination?

Neither. A special cluster type was created in Envoy. One that does not
require load balancing, but simply forwards the connection to the exact ip
for which the incoming request arrived. That’s what we use.
—

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1277#issuecomment-340801527, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AH0qd79oHlvBitgUFVLkK6QnxkAtu2spks5sxz4mgaJpZM4QL9gZ
.

First, I do not have a strong use-case, yet, to justify the need for using auth with StatefulSet, so if anybody has this, please comment on this issue.

I'm still getting started with Istio and its mutual SSL auth capabilities, so, I might be getting it wrong, but I would expect a cluster of Cassandra instances to communicate with each other via a secure channel, specially for a public cloud scenario.

By the way, this is how I'm setting it up, on a fully up-to-date Fedora 26
$ minikube start --vm-driver kvm --cpus 2 --memory 8192 --extra-config=apiserver.Admission.PluginNames="Initializers,NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,GenericAdmissionWebhook,ResourceQuota" --kubernetes-version=v1.8.0
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/master/install/kubernetes/istio-auth.yaml
$ kubectl apply -f https://raw.githubusercontent.com/istio/istio/master/install/kubernetes/istio-initializer.yaml
$ kubectl create -f https://raw.githubusercontent.com/jaegertracing/jaeger-kubernetes/master/production/cassandra.yml

After a while, this can be seen on the logs for cassandra-1:
INFO  [HANDSHAKE-cassandra-0.cassandra/<IP_ADDRESS>] 2017-11-02 12:08:57,026 OutboundTcpConnection.java:569 - Cannot handshake version with cassandra-0.cassandra/<IP_ADDRESS>
INFO  [HANDSHAKE-cassandra-0.cassandra/<IP_ADDRESS>] 2017-11-02 12:08:57,029 OutboundTcpConnection.java:560 - Handshaking version with cassandra-0.cassandra/<IP_ADDRESS>
Exception (java.lang.RuntimeException) encountered during startup: Unable to gossip with any seeds
java.lang.RuntimeException: Unable to gossip with any seeds
	at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1415)
	at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550)
	at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801)
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:666)
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:612)
	at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:393)
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600)
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689)
ERROR [main] 2017-11-02 12:08:58,049 CassandraDaemon.java:706 - Exception encountered during startup
java.lang.RuntimeException: Unable to gossip with any seeds
	at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:1415) ~[apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.StorageService.checkForEndpointCollision(StorageService.java:550) ~[apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.StorageService.prepareToJoin(StorageService.java:801) ~[apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:666) ~[apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.StorageService.initServer(StorageService.java:612) ~[apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:393) [apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:600) [apache-cassandra-3.11.1.jar:3.11.1]
	at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:689) [apache-cassandra-3.11.1.jar:3.11.1]

I'm also have this use case and am seeing the same issue trying to use Istio with auth enabled.
My team has a document based persistency store that synchronizes between members over http using a gossip scheme. It generally runs with only 3 or 5 replicas and currently resides in a StatefulSet. I was hoping to use Istio to enable mutual TLS between the pods in this StatefulSet, and also for other stateless microservices in Deployments that need to communicate back to the document store StatefulSet, but as seen by @jpkrohling the document store pods cannot access each other via their pod IPs/DNS so in a similar way the gossip and document sync fails.
I don't believe this issue is just limited to StatefulSets as I also tried using a Deployment and Service per document store pod (so 3 x deployments and 3 x services) to see if I could get the document store pods to sync but I'm not sure if it was the added latency or some thing else but the pods never quite managed to converge so the store couldn't start up properly.
For now it seems I am left with no choice but to either disable Istio Auth entirely and manage SSL certs for all of our microservices in this app, or treat this app as an external Egress and lose out on all the other Istio goodness for the document store which is a huge shame.
I believe there are a significant number of apps out there that use gossip based protocols to communicate amongst themselves and do not need to scale to 100s of pods so it would be great to see a solution for this pod to pod communication issue, even if it had some sort of maximum allowed number of pods.

Thank you @jpkrohling and @carpenterm for the realistic use cases, will bring this up in the discussions about the roadmap.

Re-opening since I think it got closed by some script.

@rshriram , the identity in Istio is not service name, it's (k8s) service account. And we are using secure naming to do service account to service name mapping validation. It's unclear to me how can we handle this without listener/cluster. But I am happy to be involved in the discussion to support this use case.

mTLS works between pods in statefulsets. See test here #6885

@rshriram doesn't look like #6885 was merged?

Hi 👋 I am having issues when attempting to use tls with a headless service/stateful set. I have attempted using both a mesh-wide policy as well as one that targets the service in question, per the Istio docs.

Can you attach the pod and service yaml so we can take a closer look? (if you can run the dump_kubernetes.sh tool and send us the dump file, it's even better)? Do you have any other services (headless or not) sharing the same endpoints with your headless service.

Hi Diem - Thanks for the help! I am not sure will be able to post the dump, but here is the pod spec and services.
Cassandra Pod:
apiVersion: v1
kind: Pod
metadata:
  annotations:
    cni.projectcalico.org/podIP: <IP_ADDRESS>/32
    kubernetes.io/psp: ips.restricted
    sidecar.istio.io/status: '{"version":"2e0c897425ef3bd2729ec5f9aead7c0566c10ab326454e8e9e2b451404aee9a5","initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","istio-certs"],"imagePullSecrets":null}'
  creationTimestamp: 2018-10-24T14:33:41Z
  generateName: cassandra-
  labels:
    app: cassandra
    controller-revision-hash: cassandra-854b8d6c84
    release: cassandra
    statefulset.kubernetes.io/pod-name: cassandra-0
  name: cassandra-0
  namespace: ips-dx
  ownerReferences:
  - apiVersion: apps/v1
    blockOwnerDeletion: true
    controller: true
    kind: StatefulSet
    name: cassandra
    uid: 1203192b-d795-11e8-bb19-12e4a8aa1008
  resourceVersion: "471372"
  selfLink: /api/v1/namespaces/ips-dx/pods/cassandra-0
  uid: cd8657f3-d799-11e8-bb19-12e4a8aa1008
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: px/running
            operator: NotIn
            values:
            - "false"
          - key: px/enabled
            operator: NotIn
            values:
            - "false"
    podAntiAffinity:
      preferredDuringSchedulingIgnoredDuringExecution:
      - podAffinityTerm:
          labelSelector:
            matchExpressions:
            - key: app
              operator: In
              values:
              - cassandra
          topologyKey: failure-domain.beta.kubernetes.io/zone
        weight: 10
      requiredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchExpressions:
          - key: app
            operator: In
            values:
            - cassandra
        topologyKey: kubernetes.io/hostname
  containers:
  - env:
    - name: MAX_HEAP_SIZE
      value: 8G
    - name: HEAP_NEWSIZE
      value: 400M
    - name: VNODES
      value: "128"
    - name: CASSANDRA_SEEDS
      value: cassandra-0.cassandra.ips-dx
    - name: CASSANDRA_AUTO_BOOTSTRAP
      value: "false"
    image: [internal reg]/cassandra-docker:3-75b0763845b42e3f706fd4856163e4a9ddc0a462
    imagePullPolicy: IfNotPresent
    name: cassandra
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/lib/cassandra
      name: cassandra-data
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: cassandra-token-jzsmr
      readOnly: true
  - args:
    - proxy
    - sidecar
    - --configPath
    - /etc/istio/proxy
    - --binaryPath
    - /usr/local/bin/envoy
    - --serviceCluster
    - cassandra
    - --drainDuration
    - 45s
    - --parentShutdownDuration
    - 1m0s
    - --discoveryAddress
    - istio-pilot.istio-system:15005
    - --discoveryRefreshDelay
    - 1s
    - --zipkinAddress
    - zipkin.istio-system:9411
    - --connectTimeout
    - 10s
    - --statsdUdpAddress
    - istio-statsd-prom-bridge.istio-system:9125
    - --proxyAdminPort
    - "15000"
    - --controlPlaneAuthPolicy
    - MUTUAL_TLS
    env:
    - name: POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: POD_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: INSTANCE_IP
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: status.podIP
    - name: ISTIO_META_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: ISTIO_META_INTERCEPTION_MODE
      value: REDIRECT
    image: docker.io/istio/proxyv2:1.0.2
    imagePullPolicy: IfNotPresent
    name: istio-proxy
    resources:
      requests:
        cpu: 10m
    securityContext:
      readOnlyRootFilesystem: true
      runAsUser: 1337
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /etc/istio/proxy
      name: istio-envoy
    - mountPath: /etc/certs/
      name: istio-certs
      readOnly: true
  dnsPolicy: ClusterFirst
  hostname: cassandra-0
  initContainers:
  - args:
    - -p
    - "15001"
    - -u
    - "1337"
    - -m
    - REDIRECT
    - -i
    - '*'
    - -x
    - ""
    - -b
    - ""
    - -d
    - ""
    image: docker.io/istio/proxy_init:1.0.2
    imagePullPolicy: IfNotPresent
    name: istio-init
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
  nodeName: ip-10-11-10-229.ec2.internal
  restartPolicy: Always
  schedulerName: stork
  securityContext:
    fsGroup: 1000
  serviceAccount: cassandra
  serviceAccountName: cassandra
  subdomain: cassandra
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - name: cassandra-data
    persistentVolumeClaim:
      claimName: cassandra-data-cassandra-0
  - name: cassandra-token-jzsmr
    secret:
      defaultMode: 420
      secretName: cassandra-token-jzsmr
  - emptyDir:
      medium: Memory
    name: istio-envoy
  - name: istio-certs
    secret:
      defaultMode: 420
      optional: true
      secretName: istio.cassandra
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: 2018-10-24T14:33:45Z
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: 2018-10-24T14:33:46Z
    status: "True"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: 2018-10-24T14:33:44Z
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: docker://b96a13efa36346362b34ad33df1cbb136ef176ab546588604240d3ec5e5b7e55
    image: [internal reg]/cassandra-docker:3-75b0763845b42e3f706fd4856163e4a9ddc0a462
    imageID: docker-pullable://[internal reg]/cassandra-docker@sha256:347c0f98db93719fc7460d83d8c0c030cd63be3e73f1eebe2944b243854bc60c
    lastState: {}
    name: cassandra
    ready: true
    restartCount: 0
    state:
      running:
        startedAt: 2018-10-24T14:33:46Z
  - containerID: docker://430907cfdd25b01535af17bb0ffdee209bef393ac7a20fb396934640b27d5008
    image: istio/proxyv2:1.0.2
    imageID: docker-pullable://istio/proxyv2@sha256:54e206530ba6ca9b3820254454e01b7592e9f986d27a5640b6c03704b3b68332
    lastState: {}
    name: istio-proxy
    ready: true
    restartCount: 0
    state:
      running:
        startedAt: 2018-10-24T14:33:46Z
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - containerID: docker://5ac4b1ee91c3032859673cc17d893577f238dda5a4f7dc338503244867223179
    image: istio/proxy_init:1.0.2
    imageID: docker-pullable://istio/proxy_init@sha256:e16a0746f46cd45a9f63c27b9e09daff5432e33a2d80c8cc0956d7d63e2f9185
    lastState: {}
    name: istio-init
    ready: true
    restartCount: 0
    state:
      terminated:
        containerID: docker://5ac4b1ee91c3032859673cc17d893577f238dda5a4f7dc338503244867223179
        exitCode: 0
        finishedAt: 2018-10-24T14:33:45Z
        reason: Completed
        startedAt: 2018-10-24T14:33:45Z
  phase: Running
  podIP: <IP_ADDRESS>
  qosClass: Burstable
  startTime: 2018-10-24T14:33:44Z

Headless Service:
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: 2018-10-24T13:59:48Z
  labels:
    app: cassandra
  name: cassandra
  namespace: ips-dx
  resourceVersion: "458503"
  selfLink: /api/v1/namespaces/ips-dx/services/cassandra
  uid: 120281ef-d795-11e8-bb19-12e4a8aa1008
spec:
  clusterIP: None
  ports:
  - name: tcp-cqlsh
    port: 9042
    protocol: TCP
    targetPort: 9042
  - name: tcp-node
    port: 7000
    protocol: TCP
    targetPort: 7000
  - name: tcp-nodetls
    port: 7001
    protocol: TCP
    targetPort: 7001
  - name: tcp-jmx
    port: 7199
    protocol: TCP
    targetPort: 7199
  - name: tcp-exporter
    port: 7070
    protocol: TCP
    targetPort: 7070
  selector:
    app: cassandra
  sessionAffinity: None
  type: ClusterIP
status:
  loadBalancer: {}

Headed Service:
apiVersion: v1
kind: Service
metadata:
  creationTimestamp: 2018-10-24T13:59:48Z
  labels:
    app: cassandra
  name: cassandra-external
  namespace: ips-dx
  resourceVersion: "458501"
  selfLink: /api/v1/namespaces/ips-dx/services/cassandra-external
  uid: 1201cdd5-d795-11e8-bb19-12e4a8aa1008
spec:
  clusterIP: <IP_ADDRESS>
  externalTrafficPolicy: Cluster
  ports:
  - name: http
    nodePort: 30914
    port: 80
    protocol: TCP
    targetPort: 80
  selector:
    app: cassandra
  sessionAffinity: None
  type: NodePort
status:
  loadBalancer: {}

Let me know if you need anything else. Thanks again!

If I understand correctly, you have 2 services sharing the same pod. Do you
have authN policy defined for both of them? My suspect is you have one
for cassandra-external
that disable mTLS. Note that, even though we use service name to select
policy target, it's actually mapped to workloads (pods) associated with
that services. So if you have multiple services sharing the same workload,
policy from only one of them will be used.
Thanks.
Diem
On Thu, Oct 25, 2018 at 8:31 PM gephcott<EMAIL_ADDRESS>wrote:

Hi Diem - Thanks for the help! I am not sure will be able to post the
dump, but here is the pod spec and services.
Cassandra Pod:
apiVersion: v1
kind: Pod
metadata:
annotations:
cni.projectcalico.org/podIP: <IP_ADDRESS>/32
kubernetes.io/psp: ips.restricted
sidecar.istio.io/status: '{"version":"2e0c897425ef3bd2729ec5f9aead7c0566c10ab326454e8e9e2b451404aee9a5","initContainers":["istio-init"],"containers":["istio-proxy"],"volumes":["istio-envoy","istio-certs"],"imagePullSecrets":null}'
creationTimestamp: 2018-10-24T14:33:41Z
generateName: cassandra-
labels:
app: cassandra
controller-revision-hash: cassandra-854b8d6c84
release: cassandra
statefulset.kubernetes.io/pod-name: cassandra-0
name: cassandra-0
namespace: ips-dx
ownerReferences:

apiVersion: apps/v1
blockOwnerDeletion: true
controller: true
kind: StatefulSet
name: cassandra
uid: 1203192b-d795-11e8-bb19-12e4a8aa1008
resourceVersion: "471372"
selfLink: /api/v1/namespaces/ips-dx/pods/cassandra-0
uid: cd8657f3-d799-11e8-bb19-12e4a8aa1008
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: px/running
operator: NotIn
values:
- "false"
- key: px/enabled
operator: NotIn
values:
- "false"
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:

podAffinityTerm:
labelSelector:
matchExpressions:
- key: app
operator: In
values:
- cassandra
topologyKey: failure-domain.beta.kubernetes.io/zone
weight: 10
requiredDuringSchedulingIgnoredDuringExecution:
labelSelector:
matchExpressions:

key: app
operator: In
values:

cassandra
topologyKey: kubernetes.io/hostname
containers:

env:

name: MAX_HEAP_SIZE
value: 8G
name: HEAP_NEWSIZE
value: 400M
name: VNODES
value: "128"
name: CASSANDRA_SEEDS
value: cassandra-0.cassandra.ips-dx
name: CASSANDRA_AUTO_BOOTSTRAP
value: "false"
image: [internal reg]/cassandra-docker:3-75b0763845b42e3f706fd4856163e4a9ddc0a462
imagePullPolicy: IfNotPresent
name: cassandra
resources: {}
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /var/lib/cassandra
name: cassandra-data
mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: cassandra-token-jzsmr
readOnly: true

args:

proxy
sidecar
--configPath
/etc/istio/proxy
--binaryPath
/usr/local/bin/envoy
--serviceCluster
cassandra
--drainDuration
45s
--parentShutdownDuration
1m0s
--discoveryAddress
istio-pilot.istio-system:15005
--discoveryRefreshDelay
1s
--zipkinAddress
zipkin.istio-system:9411
--connectTimeout
10s
--statsdUdpAddress
istio-statsd-prom-bridge.istio-system:9125
--proxyAdminPort
"15000"
--controlPlaneAuthPolicy
MUTUAL_TLS
env:
name: POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
name: POD_NAMESPACE
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.namespace
name: INSTANCE_IP
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: status.podIP
name: ISTIO_META_POD_NAME
valueFrom:
fieldRef:
apiVersion: v1
fieldPath: metadata.name
name: ISTIO_META_INTERCEPTION_MODE
value: REDIRECT
image: docker.io/istio/proxyv2:1.0.2
imagePullPolicy: IfNotPresent
name: istio-proxy
resources:
requests:
cpu: 10m
securityContext:
readOnlyRootFilesystem: true
runAsUser: 1337
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /etc/istio/proxy
name: istio-envoy
mountPath: /etc/certs/
name: istio-certs
readOnly: true
dnsPolicy: ClusterFirst
hostname: cassandra-0
initContainers:

args:

-p
"15001"
-u
"1337"
-m
REDIRECT
-i
'*'
-x
""
-b
""
-d
""
image: docker.io/istio/proxy_init:1.0.2
imagePullPolicy: IfNotPresent
name: istio-init
resources: {}
securityContext:
capabilities:
add:

NET_ADMIN
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
nodeName: ip-10-11-10-229.ec2.internal
restartPolicy: Always
schedulerName: stork
securityContext:
fsGroup: 1000
serviceAccount: cassandra
serviceAccountName: cassandra
subdomain: cassandra
terminationGracePeriodSeconds: 30
tolerations:

effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 300
effect: NoExecute
key: node.kubernetes.io/unreachable
operator: Exists
tolerationSeconds: 300
volumes:
name: cassandra-data
persistentVolumeClaim:
claimName: cassandra-data-cassandra-0
name: cassandra-token-jzsmr
secret:
defaultMode: 420
secretName: cassandra-token-jzsmr
emptyDir:
medium: Memory
name: istio-envoy
name: istio-certs
secret:
defaultMode: 420
optional: true
secretName: istio.cassandra
status:
conditions:
lastProbeTime: null
lastTransitionTime: 2018-10-24T14:33:45Z
status: "True"
type: Initialized
lastProbeTime: null
lastTransitionTime: 2018-10-24T14:33:46Z
status: "True"
type: Ready
lastProbeTime: null
lastTransitionTime: 2018-10-24T14:33:44Z
status: "True"
type: PodScheduled
containerStatuses:
containerID: docker://b96a13efa36346362b34ad33df1cbb136ef176ab546588604240d3ec5e5b7e55
image: [internal reg]/cassandra-docker:3-75b0763845b42e3f706fd4856163e4a9ddc0a462
imageID: docker-pullable://[internal reg]/cassandra-docker@sha256:347c0f98db93719fc7460d83d8c0c030cd63be3e73f1eebe2944b243854bc60c
lastState: {}
name: cassandra
ready: true
restartCount: 0
state:
running:
startedAt: 2018-10-24T14:33:46Z
containerID: docker://430907cfdd25b01535af17bb0ffdee209bef393ac7a20fb396934640b27d5008
image: istio/proxyv2:1.0.2
imageID: docker-pullable://istio/proxyv2@sha256:54e206530ba6ca9b3820254454e01b7592e9f986d27a5640b6c03704b3b68332
lastState: {}
name: istio-proxy
ready: true
restartCount: 0
state:
running:
startedAt: 2018-10-24T14:33:46Z
hostIP: <IP_ADDRESS>
initContainerStatuses:
containerID: docker://5ac4b1ee91c3032859673cc17d893577f238dda5a4f7dc338503244867223179
image: istio/proxy_init:1.0.2
imageID: docker-pullable://istio/proxy_init@sha256:e16a0746f46cd45a9f63c27b9e09daff5432e33a2d80c8cc0956d7d63e2f9185
lastState: {}
name: istio-init
ready: true
restartCount: 0
state:
terminated:
containerID: docker://5ac4b1ee91c3032859673cc17d893577f238dda5a4f7dc338503244867223179
exitCode: 0
finishedAt: 2018-10-24T14:33:45Z
reason: Completed
startedAt: 2018-10-24T14:33:45Z
phase: Running
podIP: <IP_ADDRESS>
qosClass: Burstable
startTime: 2018-10-24T14:33:44Z

Headless Service:
apiVersion: v1
kind: Service
metadata:
creationTimestamp: 2018-10-24T13:59:48Z
labels:
app: cassandra
name: cassandra
namespace: ips-dx
resourceVersion: "458503"
selfLink: /api/v1/namespaces/ips-dx/services/cassandra
uid: 120281ef-d795-11e8-bb19-12e4a8aa1008
spec:
clusterIP: None
ports:

name: tcp-cqlsh
port: 9042
protocol: TCP
targetPort: 9042
name: tcp-node
port: 7000
protocol: TCP
targetPort: 7000
name: tcp-nodetls
port: 7001
protocol: TCP
targetPort: 7001
name: tcp-jmx
port: 7199
protocol: TCP
targetPort: 7199
name: tcp-exporter
port: 7070
protocol: TCP
targetPort: 7070
selector:
app: cassandra
sessionAffinity: None
type: ClusterIP
status:
loadBalancer: {}

Headed Service:
apiVersion: v1
kind: Service
metadata:
creationTimestamp: 2018-10-24T13:59:48Z
labels:
app: cassandra
name: cassandra-external
namespace: ips-dx
resourceVersion: "458501"
selfLink: /api/v1/namespaces/ips-dx/services/cassandra-external
uid: 1201cdd5-d795-11e8-bb19-12e4a8aa1008
spec:
clusterIP: <IP_ADDRESS>
externalTrafficPolicy: Cluster
ports:

name: http
nodePort: 30914
port: 80
protocol: TCP
targetPort: 80
selector:
app: cassandra
sessionAffinity: None
type: NodePort
status:
loadBalancer: {}

Let me know if you need anything else. Thanks again!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1277#issuecomment-433275186, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX99ca-ILZLHcah_C9rYbb_xeLqPXI27ks5uooIegaJpZM4QL9gZ
.

--
Diem Vu | Software Engineer |<EMAIL_ADDRESS>| +1<PHONE_NUMBER>

Hi Diem - i do have 2 services using the same pod. I tried re-deploying cassandra with only the headless service to try to avoid the issue you mentioned above and i am still getting the same handshake error. Any other ideas?

Can you run istioctl authn tls-check and let me know what you see. Thanks
On Fri, Oct 26, 2018, 4:21 AM gephcott<EMAIL_ADDRESS>wrote:

Hi Diem - i do have 2 services using the same pod. I tried re-deploying
cassandra with only the headless service to try to avoid the issue you
mentioned above and i am still getting the same handshake error. Any other
ideas?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/1277#issuecomment-433375554, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX99cYQ6k3zIKyGCW9pLIUZYpQN9Jjugks5uovAtgaJpZM4QL9gZ
.

Sure, here is what i am seeing:
HOST:PORT                                   STATUS     SERVER     CLIENT     AUTHN POLICY     DESTINATION RULE
cassandra.ips-dx.svc.cluster.local:7000     OK         mTLS       mTLS       default/         default/ips-dx

Here is the proxy status as well:
PROXY                                                 CDS        LDS        EDS               RDS          PILOT                            VERSION
cassandra-0.ips-dx                                    SYNCED     SYNCED     SYNCED (100%)     SYNCED       istio-pilot-7f8c49bbd8-vlbtv     1.0.2
cassandra-1.ips-dx                                    SYNCED     SYNCED     SYNCED (100%)     SYNCED       istio-pilot-7f8c49bbd8-vlbtv     1.0.2
cassandra-2.ips-dx                                    SYNCED     SYNCED     SYNCED (100%)     SYNCED       istio-pilot-7f8c49bbd8-vlbtv     1.0.2

I also tried updating to 1.0.3 this morning, didn't solve the issue.

Diem - here is a dump of the 3 Cassandra pods trying to communicate with each other. Looks like they are using 7001 for the handshaking.
cass1_out.txt
cass2_out.txt
cass3_out.txt
Thanks!

Thanks for the investigation, Diem.


NIFI-2639 Update NiFi In Depth Doc: made text edits and replaced scre…

…enshots with new UI

Reviewing

+1
Read through the docs changes, compared old/new images and did a contrib check build. Looks good @andrewmlim, thanks! I will merge it in.


Install Help

You should create a YT vid on how to properly install the bot

Why though? This sounds like a terrible idea.

It's tedious, takes a lot of time to do, could be very specific depending on the setup and exact 1:1 wouldn't apply to everyone, video could be taken down, removed, god knows what else would happen with it.
Bot's code changes and so does documentation - once process for installation would get different then the video would be also outdated - would you need to create a whole new video from scratch? or keep the old one and make people follow a guide, copy exact steps and commands and then fail because things have changed since video has been published.
Already existing documentation in install-docs directory is so verbose, detailed and goes through every single step covering all possible issues you might encounter - just read it and if you didn't understand it, read it again from the beginning and I guarantee you that it's easy to install the bot thanks to these docs which even include example configuration files and systemd units.

I have a suspicion that you might be asking for a video tutorial because you‘re lacking the fundamental skills required to run a linux system or server. (If you had those skills, I‘m convinced following the written install docs would be a breeze).
For this reason I agree with zneix - if you are not able to follow the install docs just because you‘re lacking the general skills of "doing things on linux" or "administrating a linux server", then you should work on getting up to speed on that (instead of asking for an install video to follow verbatim), because that kind of knowledge is out of the scope of the pajbot project.
It would also be dangerous for us to invite inexperienced people to run a service on the open internet/run a server - wouldn‘t making a video tutorial also make it so we had to teach about how to secure the server, install security updates on it, etc..?
And last of all, we‘d be getting a whole lot more support requests for issues that are not really pajbot issues, and are more issues that general system administration knowledge could solve. (For example, if we made an install tutorial, and you got stuck on it, wouldn‘t you come to ask for help on the GitHub issues here on this project?)


New users are not able to login

New users are not able to login

New users are now able to login


OS Configurable Options

The problem is it's pretty much useless because there is no configurable option to allow the client to choose the OS when ordering. Honestly, what was the developer thinking? This is a very basic requirement for placing an order for any server right?
I know your dev is going to say just create a product for each OS. Well, let's think about that...
12 Locations x 10 server sizes x 11 OS options = 1,320 Products. I think you get the point that's not doable.

Hello, this can be done by code inspection. Look at Location and you will be able to do the operating system choice.

This is now possible due to recent update we did into module. Feel free to open a new issue in case you have notices something not working though.

I just installed the latest version, and I do not see a spot where the customer can choose the location.  I see that it can only be configured in the package itself.  Can you please let me know how I can configure this so the CUSTOMER can choose which location they want to sign up on.

Sorry closing this too early but we are just about to release an update where this is fixed.

opening as not fixed yet

Hey, apologies. We are about to release a new version of the module. This time for real. Please open a new issue if this still persists.


Add support for full 128-bit decimal divide

This depends on https://github.com/NVIDIA/spark-rapids-jni/pull/506
This fixes #6142
It also matches a bug in average for large decimal values.

build

build

build

The failure appears to be #6446 and not related to this at all.

build


[Android] Migrated app to MAUI - GetPurchasesAsync returns no results

Firstly, thank you so much for this plugin - it has been vital for me since first installing it 3 years ago. However, since MAUI migration it's failing to work as expected.
My MAUI app, migrated from Xamarin, cannot restore purchases - GetPurchasesAsync is returning no results. If instead you choose to Purchase, it finds that the item is already owned.
Version Number of Plugin: 7.1.0
Device Tested On: Android (Samsung S21)
Simulator Tested On: N/A
Version of Rider: 2023.3
Start the app, press the button to restore purchases.
The existing purchase should be found BUT instead
the app reports that there are no purchases found and thus will fail to restore (no results are returned from the GetPurchasesAsync call).
If you choose to make a purchase the app reports that the item is already owned and then the app recognises that the purchase has been made and effectively restores it.

For me GetPurchasesAsync doesn't works for iOS. It returns nothings not even throw any exception and keeps on running.

Hello James, I have the same issue with MAUI 8.0.71 and InAppBillingPlugin 8.0.2 beta , GetPurchasesAsync is not returning on iOS

My workaround was instead of calling GetPurchasesAsync function, I directly call PurchaseAsync (iOS only) and it would work fine. If user is already subscribed, it will return purchase token of that specific purchase. Otherwise it will start new purchase

Ok guys, I found the issue and I have a fix for the .net 8 branch.
In InAppBilling.ios.cs in the RestoreAsync() method (line 247) there is
return tcsTransaction.Task
change it with
var result = await tcsTransaction.Task;
return result;

to avoid issue with the finally statement that unsubscribe the handler.
From my preliminary testing, with this patch everything works fine on the iPhone.

I am not sure how that would fix anything as it would be doing the same thing....

@electro-logic will push out 8.0.3, but that isn't related to this at all as they are saying it is android

Hello James, yes my reply was to sheharyarshahid that was mentioning iOS as not working.


GetConnect grapghql subscription

May I know how to do that? Thanks.

This is the only reason I still use a graphql package in one of my projects, so I plan to add it.
Maybe in 1 or 2 releases we will have this feature

Thank you and looking forward to the feature.

which version supports graphql?

Any updates on this feature?


Be smarter with existing network names

Until now, it was more a "all or none" politic regarding the prefix
added to the network names.
This patch allows to be slightly smarter by allowing to point to actual
network names we don't want to prefix.
This is especially interesting for multi-hypervisor layout, with an OCP
cluster deployed: since ocpbm and ocppr are managed by the 3rd party
product "dev-scripts", this new feature will allow to deploy the same
networks on remote nodes, ensuring consistency in the names all the way
around.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running
[X] Appropriate documentation exists and/or is up-to-date:

[X] README in the role

/test all

Not sure if it's an issue @cjeanner but this is sharing commits with https://github.com/openstack-k8s-operators/ci-framework/pull/998

Not sure if it's an issue @cjeanner but this is sharing commits with #998

that's why I marked it as "draft" - I rebased that patch onto #998 on purpose for my local tests. Now it's all good, we're up-to-date without any trailing patch since I rebased against main after the 998 merge :)

recheck

quay.io/openstack-k8s-operators/rabbitmq-cluster-operator-bundle@sha256:2a09973faa91ae6d3913d61cc0ae7e124240c27f886563de87a2fbdd3aec6ad0...\\nError: initializing source docker://quay.io/openstack-k8s-operators/rabbitmq-cluster-operator-bundle@sha256:2a09973faa91ae6d3913d61cc0ae7e124240c27f886563de87a2fbdd3aec6ad0: can't talk to a V1 container registry\\n. exit status 125\"", "Error: error pulling image: Trying to pull quay.io/openstack-k8s-operators/rabbitmq-cluster-operator-bundle@sha256:2a09973faa91ae6d3913d61cc0ae7e124240c27f886563de87a2fbdd3aec6ad0...", "Error: initializing source docker://quay.io/openstack-k8s-operators/rabbitmq-cluster-operator-bundle@sha256:2a09973faa91ae6d3913d61cc0ae7e124240c27f886563de87a2fbdd3aec6ad0: can't talk to a V1 container registry", ". exit status 125",

recheck

/approve


Task running indicator does not appear after first terminate

VSCode Version: Version 1.0.0 (1.0.0)
OS Version: OSX 10.11.4 (15E65)

Steps to Reproduce:

Run task.
Terminate running task.
Run the task again.

Closing. I am not able to reproduce on latest.


Watch need to recompile mod.info and workshop.txt when changes happens in the project.json

Update fixing this issues is on the way.

Closed with v2.2.0
39f7c2d


No navigation drawer in About activity

Describe the bug

Navigation drawer cannot be accessed via the 'About' screen
To Reproduce
Steps to reproduce the behavior:

Open the navigation drawer.
Click on 'About'
Try accessing the navigation drawer.
Navigation drawer will not open.

Expected behavior

Navigation drawer should have come up.
Would you like to work on the issue?

[x] Yes
[ ] No

I suppose this is working fine and as intended

Actually I was thinking that the navigation drawer should be there in the AboutActivity also.

@iamareebjamal Should this be implemented?

No, it's a separate activity


proxy minio through /minio

Allows us to expose only a single port: 4443. Better for the end user

I don't think this will work because the URL signature is changing. Closing because I don't have the bandwidth to find a solution right now


Deploy Consul, Controller, Kafka, Zookeeper and Invoker in Kubernetes

Deploy Consul and seed the database.
Add all group-vars so that the properties file can be generated.
properly seed Kafka with correct invoker topics
Update deploy script to only deploy couch DB if it does not exist.
Bump deployment time for travis

This issue will check off everything but Nginx from this issue

Closing this PR. For some reason it is showing my first 2 commits as par of this PR that have already been merged. will fix this up and send a new PR

rebase to master.


Ability to add json-loader

Updates react-transform HMR check to not match json-loader.
While trying to use the color-loader package, I ran into an issue with the react-transform HMR map function, matching when including the follow loader block:
{
  test: /\.json$/,
  loader: 'json-loader'
}

Since I'm assuming it was only meant to match the babel loader.
Lastly, is there a reason you match on the test and not the loader prop?
Example:
if (/babel/.test(loader.loader)) { ... }

Seems to work as well?
Thanks

The reason for the check on test and not loader was because (way back when) I used to have multiple loaders for js files, so it made more sense to check a singular test rather than iterate through arrays. That's not so much the case anymore, but oh well.
This looks like a much-needed fix, thank you. If you have any swaying arguments for moving the check from test to loader then I'd be happy to consider an additional PR, but I don't think it's causing too many problems as it stands.

Thanks @davezuko, glad it's a fix. I really don't understand the need enough to say if the loader.loader makes more sense. If it only ever needs to match the babel loader, then it might be safer, in case someone needs to add some other loader that contains a js in the test regex. Nothing comes to mind at the moment but I imagine there are cases.
I can make a PR if you think it's a better approach. I think you mention in the source that it's a temp workaround, maybe not worth touching it anymore since it may get refactored anyway.
Thanks


A tiny change to README.md#Installing

Description
Made it obvious one has to cd into their CakePHP directory and run the composer command from it.
Summarize
Edited README.md

Current coverage is 96.11% (diff: 100%)

Merging #164 into master will not change coverage

@@             master       #164   diff @@
==========================================
  Files            12         12
  Lines           335        335
  Methods          37         37
  Messages          0          0
  Branches          0          0
==========================================
  Hits            322        322
  Misses           13         13
  Partials          0          0

Powered by Codecov. Last update 8da53d6...f1a15a5

I am not a too big fan of this, as it should be very clear when working with composer where to be for it to run (where the composer.json file is, so in the app dir).
This seems to be redundant and clear from the scope.
But meh, if it helps some people..

But meh, if it helps some people..

My thoughts exactly. There's a chance someone will stop for a second and be uncertain about that. Not everyone has as much experience with composer as you do for instance. I'm unsure what exactly is wrong with saying "your CakePHP directory", but if you feel it's not okay then so be it. Rephrased that portion.

CakePHP dir = core dir (vendor/cakephp/cakephp) = dangerous tip.
My remark wasn't about rephrasing, I was just not sure this additional note is necessary.

CakePHP dir = core dir (vendor/cakephp/cakephp) = dangerous tip.

I see what you're saying. Sorry about that then.


Dynamic change color choice name

I'm using the fuzzy prompt to list EC2 instances, the choices are a list of Choice with a value and name, the name is in this format
<instance name> | <running/stopped>

I want that the running/stopped will be in green/red colors, is it possible to change the color of the line based on the status?
Also is it possible to only change this specific part of the string to a different color? I looked at color_print but couldn't find a way using it.

Hi @arossert ,
As of the current release, this feature does not exist yet. Thanks for raising it, I'll include this in the next release.
For changing a specific part of the string, it won't happen for Choice (it'll only for the entire choice), but for color_print, you essentially have to break your characters into multiple tuples. E.g. printing hello world
color_print(formatted_text=[("blue", "hel"), ("red", "lo"), ("", " "), ("green", "wor"), ("yellow", "ld")])

Thanks,
Kevin

@kazhala thanks for the quick response.
even changing the whole choice text will be good, I did tried to look at how fuzzy prompt color part of the text in a different color as you search (it mark the found characters in pink) but I got lost ☺


docs(docs/debug.md): debug documentation

created a documentation file to sucessfully set up a vs code debugger to debug this project
#74

@sansyrox please review.


Add support for a smooth/ellipsoid terrain model

I add a Cesium3DTileset with "Cesium World Terrain + Bing Maps Aerial imagery", then I replace the Cesium ion Raster Overlay  component of the newly added Cesium3DTileset Actor with CesiumTileMapServiceRasterOverlay component, and set the CesiumTileMapServiceRasterOverlay component's url point to my local tms server, so far it woks as expected. But when I disconnect the network( I need to work offline), it can't load any tile maps. The Output Log panel shows an error as
"LogCesium: Error: [2021-05-09 10:52:10.619] [error] [Tileset.cpp:142] Received status code 401 for asset response https://api.cesium.com/v1/assets/0/endpoint",
I guess that the Cesium3DTileset need to load the tileset.json, then the CesiumTileMapServiceRasterOverlay will work. But how can I just use  the CesiumTileMapServiceRasterOverlay offline without the need to load any tileset.json, because I don't need any tilesets like terrain or 3D models.

Closed by #908


add new hacktoberfest badge to our readme

Let's include the new Hacktoberfest badge created in #4109 to our readme!

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

:book:

Thanks for contributing to our documentation. We :heart: our documentarians!

  Generated by :no_entry_sign: dangerJS against 54dbe45764507e5d90d8a0c580bde27fcad6a65e


Baron Blue (Certified Connector)

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[ ] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[ ] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[ ] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[ ] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

Hello @mtgomes,
Thank you very much and congratulations on your new submission. Our Certification Engineers will review it within 1-2 weeks.
Please let us know if you have any questions.
Thank you very much again for working with us.

Thanks for the feedback. Please let me know if I can help with something.

Thanks for the feedback, and please let me know if there's anything I can do.

Hello @mtgomes,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Hi @v-EgorKozhadei, thanks for following back. I'm sorry for taking a bit to reply. Many things are going on, and I kept pushing this a bit. I will probably need to rename the connector (branding issues, but all the rest stay the same), so I'll probably need to re-submit everything. Sorry, but things are going fast.
All your comments were excellent, and I'll fix them for the next version if that's ok with you.

Hello @mtgomes,
I hope you are doing well.
I am following up with you to see if you need any help with updating your connector artifacts.
Please do not hesitate to reach out to me if you have any questions as we are always here to help. 😊
I look forward to hearing from you.
Thank you very much.

Hello @mtgomes,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Thanks for reaching out.
I needed to put a bit on hold while I tackle other topics, but I’ll be back working on it soon.
Thanks a lot!
Manuel T Gomes
Founder, SKILLFUL SARDINE
https://skillfulsardine.com
https://manueltgomes.com/
On 18 Oct 2022, at 07:23, Amjed Ayoub<EMAIL_ADDRESS>wrote:
Hello @mtgomeshttps://github.com/mtgomes,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/1909#issuecomment-1281830807, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAQGJ45COUICQGK3RKOCCPDWDYX5DANCNFSM57PW64EQ.
You are receiving this because you were mentioned.Message ID: @.***>

Hi @mtgomes thank you so much for getting back to me.
I hope everything will work out well for you. In the meantime, please do not hesitate to reach out to us if you have any questions.
Thank you so much again.

Hello @mtgomes,
I hope you are doing well.
I am following up in my messages below to see if you need any help with updating your connector artifacts.
Please do not hesitate to reach out to me if you have any questions as we are always here to help. 😊
I look forward to hearing from you.
Thank you very much.

Hello Partners,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Hi,
Thanks for getting in touch and happy new year to you.
Can you please advise on what I should do to change the connector's name?
I’ve submitted it with a name, but I’m going to change it and probably split it into multiple ones.
Can you please advise?
[signature_2604816957]
Manuel T Gomes
CEO / Founder,
SKILLFUL SARDINE
https://skillfulsardine.com
https://manueltgomes.com/
From: Amjed Ayoub @.>
Date: Friday, 30 December 2022 at 17:55
To: microsoft/PowerPlatformConnectors @.>
Cc: Manuel Gomes @.>, Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Baron Blue (Certified Connector) (PR #1909)
Hello Partners,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/PowerPlatformConnectors/pull/1909#issuecomment-1368032390, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAQGJ42T7IAMQQRAYQD4EVTWP4OZ3ANCNFSM57PW64EQ.
You are receiving this because you were mentioned.Message ID: @.***>

Hi, Thanks for getting in touch and happy new year to you. Can you please advise on what I should do to change the connector's name? I’ve submitted it with a name, but I’m going to change it and probably split it into multiple ones. Can you please advise? [signature_2604816957] Manuel T Gomes CEO / Founder, SKILLFUL SARDINE https://skillfulsardine.com https://manueltgomes.com/ From: Amjed Ayoub @.> Date: Friday, 30 December 2022 at 17:55 To: microsoft/PowerPlatformConnectors @.> Cc: Manuel Gomes @.>, Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] Baron Blue (Certified Connector) (PR #1909) Hello Partners, I hope you are doing well. I am following up with you to see how things are going with preparing your connector. Please let us know if you have any questions. Thank you. — Reply to this email directly, view it on GitHub<#1909 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAQGJ42T7IAMQQRAYQD4EVTWP4OZ3ANCNFSM57PW64EQ. You are receiving this because you were mentioned.Message ID: @.***>

@mtgomes can you please elaborate more on this? the current title is valid.

@mtgomes please resolve all conversations. Thank you so much.

Hello @mtgomes,
I hope you are doing well.
I am following up with you to see how things are going with preparing your connector.
Please let us know if you have any questions.
Thank you.

Hi!
Thanks for reaching out and for all the help so far.
I needed to stop the development but I’ll resume it again in the next few months.
Thanks again for the help and for your patience in waiting for the information.
—
Manuel
From: Amjed Ayoub @.>
Date: Wednesday, 1 March 2023 at 22:03
To: microsoft/PowerPlatformConnectors @.>
Cc: Manuel Gomes @.>, Mention @.>
Subject: Re: [microsoft/PowerPlatformConnectors] Baron Blue (Certified Connector) (PR #1909)
Hello @mtgomeshttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmtgomes&data=05|01|manuel%40manueltgomes.com|f07af515b60249eb21f808db1a98614c|aeec6d42e51b47199888120ce4e5e222|0|0|638133013993026486|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=axdQa8on8hif%2BKBDTY5XsUvjy082ylRjIm5us%2BQ%2BynQ%3D&reserved=0,
I hope you are doing well.
I am following up on my messages to see if you need any help with updating your connector artifacts.
Please do not hesitate to reach out to me if you have any questions as we are always here to help. 😊
I look forward to hearing from you.
Thank you very much.
—
Reply to this email directly, view it on GitHubhttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FPowerPlatformConnectors%2Fpull%2F1909%23issuecomment-1450843216&data=05|01|manuel%40manueltgomes.com|f07af515b60249eb21f808db1a98614c|aeec6d42e51b47199888120ce4e5e222|0|0|638133013993026486|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=qawyFnqKZD7xD5r%2BNL7PVzkh5CiEQZ0rTmYCUtqzIsc%3D&reserved=0, or unsubscribehttps://eur06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAQGJ4ZIED6TGQJJW7UHROLWZ62RJANCNFSM57PW64EQ&data=05|01|manuel%40manueltgomes.com|f07af515b60249eb21f808db1a98614c|aeec6d42e51b47199888120ce4e5e222|0|0|638133013993026486|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=lfRNTiTsBbyX2n3G6mZu7%2BtQyjxh9jbbn1gA6SD6cVI%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>

@mtgomes thank you so much for the confirmation.
We will close this PR, and in the meantime please so not hesitate to reach out to us once your connector is ready for certification.
Thank you so much again.


[stable/kube-downscaler]: match image.tag with appVersion

Description
The appVersion in kube-downscaler was updated in #293 but the image.tag value still deploys the 21.2.0 version. This updates image.tag to match appVersion.
Checklist

[x] Title of the PR starts with chart name (e.g. [stable/mychartname])
[x] I have read the contribution instructions, bumped chart version and regenerated the docs
[x] Github actions are passing

Additional Notes
It might be preferable to use the default hack from helm create so we only need to set the appVersion. I can prepare such a PR if that should be preferred.
There is also a newer version 22.7.1 on codeberg, in the spirit of atmic changes, this only fixes releasing the current appVersion but i'll prepare a PR to bump downscaler as well once this is fixed.

thanks for the quick turnaround, @max-rocket-internet :+1:
i'll follow up on my notes asap


Allow use http-banker for bidding agent example

Hello guys. First of all - Merry Christmas. I noticed, that you already have a PR(#225) with such ability. However, @oktal suggested to reimplement it using SlaveBankerArguments component. Since #225 got stuck, I implemented it by myself. Please review it, when you have a chance.

Conflicts will happen no-matter what I don't think we should hold back the PR because of this. Is there any other concerns related to this PR or can we merge it in?