Bugfix: Days of the week in history are misleading

In the history sidebar, days of the week appear as follows (for this example, assume that "Today" is a Wednesday):
11/27, Last Friday, Last Monday, Tuesday, Wednesday, Thursday, Friday, Monday, Yesterday, Current
This is confusing because it lists days from the previous week as though they were days from the current week. A more straightforward ordering (IMO) would be:
11/27, 11/28, Last Monday, Last Tuesday, Last Wednesday, Last Thursday, Last Friday, Monday, Yesterday, Current
So, today is listed as Current
Previous day is Yesterday
All other days in the current week are listed by their day names
Days in the previous week are listed by day name, prefixed with Last
Days from 2 or more weeks ago are listed in MM/DD format.

I'm going to close this, since the v2 rewrite has now been released and this bug is not present there. Please file a new issue for any new bugs you notice in v2!

I'm going to close this, since the v2 rewrite has now been released and this bug is not present there. Please file a new issue for any new bugs you notice in v2!


Bug: 安装错误 sass-embedded

Description
[Description of the bug]
Steps to Reproduce
bundle install --path vendor/bundle
[DEPRECATED] The --path flag is deprecated because it relies on being remembered across bundler invocations, which bundler will no longer do in future versions. Instead please use bundle config set --local path 'vendor/bundle', and stop using this flag
Fetching gem metadata from https://rubygems.org/..........
Resolving dependencies..........
Using rake 10.5.0
Using bundler 2.3.26
Using concurrent-ruby 1.1.10
Using public_suffix 5.0.1
Using minitest 5.16.3
Using colorator 1.1.0
Using eventmachine 1.2.7
Using http_parser.rb 0.8.0
Using ffi 1.15.5
Using forwardable-extended 2.6.0
Using google-protobuf 3.21.12 (x86_64-linux)
Using gemoji 4.0.1
Using racc 1.6.2
Using rb-fsevent 0.11.2
Using rexml 3.2.5
Using liquid 4.0.3
Using mercenary 0.4.0
Using rouge 4.0.1
Using unicode-display_width 2.3.0
Using safe_yaml 1.0.5
Using jekyll-paginate 1.1.0
Using webrick 1.7.0
Using i18n 1.12.0
Using tzinfo 2.0.5
Using addressable 2.8.1
Using em-websocket 0.5.3
Using pathutil 0.16.2
Using rb-inotify 0.10.1
Using nokogiri 1.13.10 (x86_64-linux)
Using kramdown 2.4.0
Using terminal-table 3.0.2
Using activesupport 7.0.4
Using listen 3.7.1
Using kramdown-parser-gfm 1.1.0
Using html-pipeline 2.14.3
Using jekyll-watch 2.2.1
Installing sass-embedded 1.57.1 with native extensions
It is a security vulnerability to allow your home directory to be world-writable, and bundler cannot continue.
You should probably consider fixing this issue by running chmod o-w ~ on *nix.
Please refer to https://ruby-doc.org/stdlib-3.1.2/libdoc/fileutils/rdoc/FileUtils.html#method-c-remove_entry_secure for details.
Bundler::PathError: Please fix the world-writable issue with your
/mnt/e/onedrive/project/jekyll-TeXt-theme/vendor/bundle/ruby/3.0.0/gems/sass-embedded-1.57.1
directory
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler.rb:338:in rescue in rm_rf'   /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler.rb:329:in rm_rf'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/rubygems_gem_installer.rb:111:in
strict_rm_rf' /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/rubygems_gem_installer.rb:19:in install'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/source/rubygems.rb:207:in
install' /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/installer/gem_installer.rb:54:in install'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/installer/gem_installer.rb:16:in
install_from_spec' /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/installer/parallel_installer.rb:186:in do_install'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/installer/parallel_installer.rb:177:in
block in worker_pool'   /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/worker.rb:62:in apply_func'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/worker.rb:57:in block in process_queue'   /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/worker.rb:54:in loop'
/var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/worker.rb:54:in process_queue' /var/lib/gems/3.0.0/gems/bundler-2.3.26/lib/bundler/worker.rb:91:in block (2 levels)
in create_threads'
An error occurred while installing sass-embedded (1.57.1), and Bundler cannot
continue.
In Gemfile:
jekyll-text-theme was resolved to 2.2.6, which depends on
jekyll-feed was resolved to 0.17.0, which depends on
jekyll was resolved to 4.3.1, which depends on
jekyll-sass-converter was resolved to 3.0.0, which depends on
sass-embedded
Expected behavior
[What you expected to happen]
Screenshots (If Necessary)
[Screenshots to help explain your problem.]
Environment (If Necessary)

OS: wsl2 ubuntu 22.04
Ruby: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
Jekyll: [e.g. Github Pages, 3.7.3]
Browser: [e.g. Chrome, Safari, Edge, Firefox]

same problem

在Gemfile文件, 添加gem "jekyll-sass-converter", "<3.0.0", 限制jekyll-sass-converter自动更新到3.0.0, 暂时解决


Is llm.bind(stop=["\nObservation"]) really meanful in json_chat agnet?

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.

Example Code

Description
https://github.com/langchain-ai/langchain/blob/ef75bb63ce5cc4fb76ba1631ebe582f56103ab7e/libs/langchain/langchain/agents/json_chat/base.py#L151
this seems useless because chat-json depends json to work,not this sort of completion
System Info

Related Components

[ ] LLMs/Chat Models
[ ] Embedding Models
[ ] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[X] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[ ] Callbacks/Tracing
[ ] Async

This is also breaking certain LLMs (i.e. using Bedrock w/ Llama2 or Titan these preconfigured stop sequences aren't allowed.
 Stop sequence key name for meta is not supported.

Stop sequence key name for meta is not supported     I am also getting this error any update @steve-carpenter

Stop sequence key name for meta is not supported  I am also getting this error using the Bedrock meta-model. Could you let me know if you have any solution? @steve-carpenter

pass stop_sequence=False when constructing the agent

How can I determine which models support stop sequences and which don't? @calvinweb

``I'm using crewai and mot of models failed
Only claud model worked form me, others gave me errors related :

[stop_sequences] is not permitted
Malformed input request: : string [Observation] does not match pattern ^(\|+|User:)

This worked for me:
from langchain_community.chat_models import BedrockChat

llm = BedrockChat(model_id="anthropic.claude-3-haiku-20240307-v1:0")


Contentful is not loading the images from the same model

I am creating the same model as defined inside vault package. but the images are not loading.
Btw I love how clean you write code 👍  😃

figured it out. Thanks anyway 👍


collisions

I got something like "collision between /nix/store/cviz20jv8f1vs9pi9md64cvw39z5a85z-util-linux-2.26.2/bin/mount' and /nix/store/vh8554xqwr9aip4l0r2q9q0712mip237-util-linux-2.26.2/bin/mount'" on each time I install something by nixos-rebuild switch.
I have utillinuxCurses in systemPackages.

utillinux (without curses) is added automatically, so they collide. I think using (hiPrio utillinuxCurses) instead should make it work.

(triage) Close @vcunat?

Can't check right now, but @vcunat answer should solve this issue, thanks.


V2: dataclasses

dataclass validation should get MASSIVELY easier and more performant since we have the arguments validator in pydantic-core which means we can do validation before constructing the dataclass. Lots of examples in the docs here.
I think we should remove all the __post_init_post_parse__ shit, and just use validation functions and the standard stuff offered by dataclasses.
@PrettyWood as the master of dataclasses, would be willing to work on this? If not, I quite understand, please remove yourself as assignee and hopefully someone else can take over.
Either way, I'd love your insights on what we should do.

(Also, https://github.com/pydantic/pydantic/issues/5271 tracks a few remaining things.)


Desktop Modeler unable to connect to self managed over tls

Describe the bug
When creating a self managed environment with a nginx ingress and rules to access the zeebe-gateway over a tls encrypted connection to port 443, I'm able to connect with zbctl, but not with Desktop Modeler.
Update: 5/5, we were able to successfully deploy from Desktop Modeler to an environment created on Azure with lets encrypt cerficiates. So, this seems intermittent. I'm not sure exactly what the root cause is.
I've reproduced this in 2 environments: SM 8.1.7 in Google Cloud, and, just today, SM 8.2.3 in Azure.
In the Google environment, I had oauth2 enabled and this command worked fine:
zbctl deploy customer_onboarding_en.bpmn \
  --address gke.upgradingdave.com:443 \
  --clientId zeebe \
  --clientSecret xxx \
  --authzUrl https://gke.upgradingdave.com/auth/realms/camunda-platform/protocol/openid-connect/token

But, Desktop Modeler would not connect:

And today we saw similar behavior in an Azure environment that @superbeagle created. This environment was configured with tls (no oauth2).  We were able to connect via zbctl:
zbctl status --address joe01.azure.upgradingdave.com:443

But Desktop modeler was not able to connect:

Steps to reproduce

Setup a self managed environment.
Provision valid ssl certificates. In my tests, I used letsencrypt.
Attempt to deploy from Desktop Modeler. In my tests, Desktop Modeler UI shows that it can't connect:

And the Desktop Modeler logs show error messages like this:
2023-03-29T16:02:12.682Z  ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: {
    type: 'oauth',
    url: '[https://gke.upgradingdave.com:443](https://gke.upgradingdave.com/)',
    clientId: 'zeebe',
    oauthURL: 'https://gke.upgradingdave.com/auth/realms/camunda-platform/protocol/openid-connect/token'
  }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:135:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:305:47
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}

Expected behavior
If a valid letsencrypt production certificate is used for a secure zeebe gateway, then Desktop Modeler should be able to connect and deploy the same as zbctl.
Environment

OS: Mac OSX 12.6.3
Camunda Modeler Version: reproduced with 5.8, 5.9, and 5.10
Execution Platform: C8SM on Google Cloud and Azure
Installed plug-ins: none

Additional context
I was able to change some lines of code in app/lib/zeebe-api/zeebe-api.js and make a custom build of Desktop Modeler that demonstrates the issue and a possible work around, I'll follow up by publishing a PR with that code

Joe created another environment this morning on Azure using Lets Encrypt production ssl certificates and we were both able to connect to this environment from Desktop Modeler:
https://joepappas.eastus.cloudapp.azure.com:443
So, this appears to be intermittent? The main difference I can see here is using eastus.cloudapp.azure.com rather than azure.upgradingdave.com. Long shot guess - perhaps it has something to do with which domain name is used?

Hi, have you tried using the --zeebe-ssl-certificate flag? This is the usual way of handling custom certs. https://docs.camunda.io/docs/next/components/modeler/desktop-modeler/flags/#zeebe-ssl-certificate

You're indicating in the issue:

Update: 5/5, we were able to successfully deploy from Desktop Modeler to an environment created on Azure with lets encrypt cerficiates. So, this seems intermittent. I'm not sure exactly what the root cause is.

Can you confirm this works with a vanilla (clean) v5.10 installation?

Hi @nikku , I tested with 5.10.0 and can reproduce this issue.
I have an environment running here:
https://aws.upgradingdave.com
I can connect from zbctl:

But I can not connect from desktop modeler:

I'll leave this environment running for next 12 hours or so in case you'd like to confirm?

Hi, I was able to deploy test.bpmn to your environment with Camunda Modeler 5.11.0 on MacOS.

@upgradingdave I was able to deploy to the remote installation (https://aws.upgradingdave.com:443) using Camunda Modeler v5.10.0 and v5.11.0 (Linux).

Marking this as needs more information as we were unable to reproduce this on a recent clean Camunda Modeler installation.

Hi @nikku and @barmac, thanks much for all your help - it's very interesting that you both can deploy to this environment, but I cannot, so maybe there's something specific to my Macbook?
Here are the logs after setting ZEEBE_NODE_LOG_LEVEL=DEBUG GRPC_VERBOSITY=DEBUG GRPC_TRACE=all
10:22:32.231 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
10:22:35.239 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:22:37.247Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [42] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:22:37.248Z | resolving_call | [42] Created
D 2023-05-11T08:22:37.248Z | resolving_call | [42] Deadline: Infinity
D 2023-05-11T08:22:37.249Z | resolving_call | [42] start called
D 2023-05-11T08:22:37.250Z | resolving_call | [42] startRead called
D 2023-05-11T08:22:37.251Z | resolving_call | [42] write() called with message of length 0
D 2023-05-11T08:22:37.251Z | resolving_call | [42] halfClose called
D 2023-05-11T08:22:37.251Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [43] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:37.251Z | retrying_call | [43] start called
D 2023-05-11T08:22:37.252Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [44] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:37.252Z | retrying_call | [43] Created child call [44] for attempt 1
D 2023-05-11T08:22:37.252Z | load_balancing_call | [44] start called
D 2023-05-11T08:22:37.252Z | load_balancing_call | [44] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:22:37.252Z | load_balancing_call | [44] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:37.252Z | retrying_call | [43] Received status from child [44]
D 2023-05-11T08:22:37.252Z | retrying_call | [43] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [44] in state ACTIVE
D 2023-05-11T08:22:37.252Z | retrying_call | [43] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:37.253Z | retrying_call | [43] startRead called
D 2023-05-11T08:22:37.254Z | retrying_call | [43] write() called with message of length 5
D 2023-05-11T08:22:37.254Z | retrying_call | [43] halfClose called
D 2023-05-11T08:22:37.254Z | resolving_call | [42] ended with status: code=14 details="No connection established"
10:22:37.255 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
D 2023-05-11T08:22:37.723Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:37.726Z | pick_first | TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:37.726Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:37.726Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:37.953Z | subchannel | (15) <IP_ADDRESS>:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:37.954Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:37.954Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:37.954Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:37.954Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:37.954Z | subchannel_refcount | (15) <IP_ADDRESS>:443 refcount 2 -> 1
D 2023-05-11T08:22:37.954Z | pick_first | TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:37.954Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:37.954Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
10:22:40.263 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:22:42.268Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [45] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:22:42.269Z | resolving_call | [45] Created
D 2023-05-11T08:22:42.269Z | resolving_call | [45] Deadline: Infinity
D 2023-05-11T08:22:42.270Z | resolving_call | [45] start called
D 2023-05-11T08:22:42.271Z | pick_first | Connect to address list <IP_ADDRESS>:443
D 2023-05-11T08:22:42.271Z | subchannel_refcount | (15) <IP_ADDRESS>:443 refcount 1 -> 2
D 2023-05-11T08:22:42.271Z | pick_first | Start connecting to subchannel with address <IP_ADDRESS>:443
D 2023-05-11T08:22:42.271Z | pick_first | IDLE -> CONNECTING
D 2023-05-11T08:22:42.271Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 IDLE -> CONNECTING
D 2023-05-11T08:22:42.271Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 IDLE -> CONNECTING
D 2023-05-11T08:22:42.272Z | resolving_call | [45] startRead called
D 2023-05-11T08:22:42.272Z | resolving_call | [45] write() called with message of length 0
D 2023-05-11T08:22:42.272Z | resolving_call | [45] halfClose called
D 2023-05-11T08:22:42.273Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [46] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:42.273Z | retrying_call | [46] start called
D 2023-05-11T08:22:42.273Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [47] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:42.274Z | retrying_call | [46] Created child call [47] for attempt 1
D 2023-05-11T08:22:42.274Z | load_balancing_call | [47] start called
D 2023-05-11T08:22:42.274Z | load_balancing_call | [47] Pick result: QUEUE subchannel: null status: undefined undefined
D 2023-05-11T08:22:42.274Z | channel | (12) dns:aws.upgradingdave.com:443 callRefTimer.ref | configSelectionQueue.length=0 pickQueue.length=1
D 2023-05-11T08:22:42.274Z | retrying_call | [46] startRead called
D 2023-05-11T08:22:42.274Z | load_balancing_call | [47] startRead called
D 2023-05-11T08:22:42.275Z | retrying_call | [46] write() called with message of length 5
D 2023-05-11T08:22:42.275Z | load_balancing_call | [47] write() called with message of length 5
D 2023-05-11T08:22:42.276Z | retrying_call | [46] halfClose called
D 2023-05-11T08:22:42.276Z | subchannel | (15) <IP_ADDRESS>:443 IDLE -> CONNECTING
D 2023-05-11T08:22:42.276Z | pick_first | CONNECTING -> CONNECTING
D 2023-05-11T08:22:42.276Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> CONNECTING
D 2023-05-11T08:22:42.276Z | channel | (12) dns:aws.upgradingdave.com:443 callRefTimer.unref | configSelectionQueue.length=0 pickQueue.length=0
D 2023-05-11T08:22:42.276Z | load_balancing_call | [47] Pick result: QUEUE subchannel: null status: undefined undefined
D 2023-05-11T08:22:42.276Z | channel | (12) dns:aws.upgradingdave.com:443 callRefTimer.ref | configSelectionQueue.length=0 pickQueue.length=1
D 2023-05-11T08:22:42.276Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> CONNECTING
D 2023-05-11T08:22:42.494Z | subchannel | (15) <IP_ADDRESS>:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:42.494Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:42.494Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:42.494Z | channel | (12) dns:aws.upgradingdave.com:443 callRefTimer.unref | configSelectionQueue.length=0 pickQueue.length=0
D 2023-05-11T08:22:42.494Z | load_balancing_call | [47] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:22:42.495Z | load_balancing_call | [47] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:42.495Z | retrying_call | [46] Received status from child [47]
D 2023-05-11T08:22:42.495Z | retrying_call | [46] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [47] in state ACTIVE
D 2023-05-11T08:22:42.495Z | retrying_call | [46] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:42.495Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:42.495Z | resolving_call | [45] ended with status: code=14 details="No connection established"
10:22:42.496 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
10:22:45.499 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:22:47.512Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [48] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:22:47.512Z | resolving_call | [48] Created
D 2023-05-11T08:22:47.513Z | resolving_call | [48] Deadline: Infinity
D 2023-05-11T08:22:47.513Z | resolving_call | [48] start called
D 2023-05-11T08:22:47.514Z | resolving_call | [48] startRead called
D 2023-05-11T08:22:47.514Z | resolving_call | [48] write() called with message of length 0
D 2023-05-11T08:22:47.515Z | resolving_call | [48] halfClose called
D 2023-05-11T08:22:47.515Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [49] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:47.515Z | retrying_call | [49] start called
D 2023-05-11T08:22:47.515Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [50] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:47.516Z | retrying_call | [49] Created child call [50] for attempt 1
D 2023-05-11T08:22:47.516Z | load_balancing_call | [50] start called
D 2023-05-11T08:22:47.516Z | load_balancing_call | [50] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:22:47.516Z | load_balancing_call | [50] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:47.516Z | retrying_call | [49] Received status from child [50]
D 2023-05-11T08:22:47.516Z | retrying_call | [49] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [50] in state ACTIVE
D 2023-05-11T08:22:47.516Z | retrying_call | [49] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:47.517Z | retrying_call | [49] startRead called
D 2023-05-11T08:22:47.517Z | retrying_call | [49] write() called with message of length 5
D 2023-05-11T08:22:47.518Z | retrying_call | [49] halfClose called
D 2023-05-11T08:22:47.518Z | resolving_call | [48] ended with status: code=14 details="No connection established"
10:22:47.519 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
10:22:50.527 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:22:52.535Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [51] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:22:52.535Z | resolving_call | [51] Created
D 2023-05-11T08:22:52.535Z | resolving_call | [51] Deadline: Infinity
D 2023-05-11T08:22:52.535Z | resolving_call | [51] start called
D 2023-05-11T08:22:52.538Z | resolving_call | [51] startRead called
D 2023-05-11T08:22:52.539Z | resolving_call | [51] write() called with message of length 0
D 2023-05-11T08:22:52.540Z | resolving_call | [51] halfClose called
D 2023-05-11T08:22:52.544Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [52] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:52.544Z | retrying_call | [52] start called
D 2023-05-11T08:22:52.545Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [53] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:52.548Z | retrying_call | [52] Created child call [53] for attempt 1
D 2023-05-11T08:22:52.549Z | load_balancing_call | [53] start called
D 2023-05-11T08:22:52.549Z | load_balancing_call | [53] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:22:52.550Z | load_balancing_call | [53] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:52.550Z | retrying_call | [52] Received status from child [53]
D 2023-05-11T08:22:52.550Z | retrying_call | [52] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [53] in state ACTIVE
D 2023-05-11T08:22:52.550Z | retrying_call | [52] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:52.551Z | retrying_call | [52] startRead called
D 2023-05-11T08:22:52.551Z | retrying_call | [52] write() called with message of length 5
D 2023-05-11T08:22:52.552Z | retrying_call | [52] halfClose called
D 2023-05-11T08:22:52.552Z | resolving_call | [51] ended with status: code=14 details="No connection established"
10:22:52.554 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
D 2023-05-11T08:22:53.808Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:53.810Z | pick_first | TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:53.810Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:53.811Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:22:54.039Z | subchannel | (15) <IP_ADDRESS>:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:54.039Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:54.040Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:54.040Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:54.040Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:54.040Z | subchannel_refcount | (15) <IP_ADDRESS>:443 refcount 2 -> 1
D 2023-05-11T08:22:54.040Z | pick_first | TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:54.040Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:54.040Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:22:55.157Z | dns_resolver | Looking up DNS hostname aws.upgradingdave.com
D 2023-05-11T08:22:55.160Z | dns_resolver | Resolved addresses for target dns:aws.upgradingdave.com:443: [<IP_ADDRESS>:443]
D 2023-05-11T08:22:55.161Z | pick_first | Connect to address list <IP_ADDRESS>:443
D 2023-05-11T08:22:55.162Z | subchannel_refcount | (15) <IP_ADDRESS>:443 refcount 1 -> 2
D 2023-05-11T08:22:55.163Z | pick_first | Start connecting to subchannel with address <IP_ADDRESS>:443
D 2023-05-11T08:22:55.163Z | pick_first | IDLE -> CONNECTING
D 2023-05-11T08:22:55.163Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 IDLE -> CONNECTING
D 2023-05-11T08:22:55.163Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 IDLE -> CONNECTING
D 2023-05-11T08:22:55.164Z | subchannel | (15) <IP_ADDRESS>:443 IDLE -> CONNECTING
D 2023-05-11T08:22:55.165Z | pick_first | CONNECTING -> CONNECTING
D 2023-05-11T08:22:55.165Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> CONNECTING
D 2023-05-11T08:22:55.165Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> CONNECTING
D 2023-05-11T08:22:55.383Z | subchannel | (15) <IP_ADDRESS>:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:55.384Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:55.384Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:22:55.384Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
10:22:55.564 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:22:57.588Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [54] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:22:57.589Z | resolving_call | [54] Created
D 2023-05-11T08:22:57.589Z | resolving_call | [54] Deadline: Infinity
D 2023-05-11T08:22:57.590Z | resolving_call | [54] start called
D 2023-05-11T08:22:57.592Z | resolving_call | [54] startRead called
D 2023-05-11T08:22:57.592Z | resolving_call | [54] write() called with message of length 0
D 2023-05-11T08:22:57.592Z | resolving_call | [54] halfClose called
D 2023-05-11T08:22:57.592Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [55] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:57.592Z | retrying_call | [55] start called
D 2023-05-11T08:22:57.593Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [56] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:22:57.593Z | retrying_call | [55] Created child call [56] for attempt 1
D 2023-05-11T08:22:57.593Z | load_balancing_call | [56] start called
D 2023-05-11T08:22:57.593Z | load_balancing_call | [56] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:22:57.593Z | load_balancing_call | [56] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:57.593Z | retrying_call | [55] Received status from child [56]
D 2023-05-11T08:22:57.593Z | retrying_call | [55] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [56] in state ACTIVE
D 2023-05-11T08:22:57.594Z | retrying_call | [55] ended with status: code=14 details="No connection established"
D 2023-05-11T08:22:57.594Z | retrying_call | [55] startRead called
D 2023-05-11T08:22:57.594Z | retrying_call | [55] write() called with message of length 5
D 2023-05-11T08:22:57.594Z | retrying_call | [55] halfClose called
D 2023-05-11T08:22:57.594Z | resolving_call | [54] ended with status: code=14 details="No connection established"
10:22:57.595 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
10:23:00.597 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
D 2023-05-11T08:23:02.617Z | channel | (12) dns:aws.upgradingdave.com:443 createResolvingCall [57] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:23:02.617Z | resolving_call | [57] Created
D 2023-05-11T08:23:02.618Z | resolving_call | [57] Deadline: Infinity
D 2023-05-11T08:23:02.618Z | resolving_call | [57] start called
D 2023-05-11T08:23:02.618Z | resolving_call | [57] startRead called
D 2023-05-11T08:23:02.618Z | resolving_call | [57] write() called with message of length 0
D 2023-05-11T08:23:02.618Z | resolving_call | [57] halfClose called
D 2023-05-11T08:23:02.618Z | channel | (12) dns:aws.upgradingdave.com:443 createRetryingCall [58] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:23:02.618Z | retrying_call | [58] start called
D 2023-05-11T08:23:02.618Z | channel | (12) dns:aws.upgradingdave.com:443 createLoadBalancingCall [59] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:23:02.618Z | retrying_call | [58] Created child call [59] for attempt 1
D 2023-05-11T08:23:02.618Z | load_balancing_call | [59] start called
D 2023-05-11T08:23:02.618Z | load_balancing_call | [59] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:23:02.618Z | load_balancing_call | [59] ended with status: code=14 details="No connection established"
D 2023-05-11T08:23:02.618Z | retrying_call | [58] Received status from child [59]
D 2023-05-11T08:23:02.619Z | retrying_call | [58] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [59] in state ACTIVE
D 2023-05-11T08:23:02.619Z | retrying_call | [58] ended with status: code=14 details="No connection established"
D 2023-05-11T08:23:02.619Z | retrying_call | [58] startRead called
D 2023-05-11T08:23:02.619Z | retrying_call | [58] write() called with message of length 5
D 2023-05-11T08:23:02.619Z | retrying_call | [58] halfClose called
D 2023-05-11T08:23:02.619Z | resolving_call | [57] ended with status: code=14 details="No connection established"
10:23:02.623 | zeebe |  INFO: Set Grpc channel failure timer for 3000ms
ERROR app:zeebe-api Failed to connect with config (secrets omitted): {
  endpoint: { type: 'selfHosted', url: 'https://aws.upgradingdave.com:443' }
} Error: 14 UNAVAILABLE: No connection established
    at callErrorFromStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call.js:31:19)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:192:76)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:78:35
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:97:36)
    at InterceptingListenerImpl.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/call-interface.js:73:23)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:360:141)
    at Object.onReceiveStatus (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:323:181)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/resolving-call.js:94:78
    at process.processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:160:34)
    at ServiceClientImpl.<anonymous> (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:105:19)
    at /Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:270:47 {
  code: 14,
  details: 'No connection established',
  metadata: Metadata { internalRepr: Map(0) {}, options: {} },
  progress: 'PROCESSED'
}
D 2023-05-11T08:23:04.039Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:23:04.040Z | pick_first | TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:23:04.040Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:23:04.040Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> CONNECTING
D 2023-05-11T08:23:04.261Z | subchannel | (15) <IP_ADDRESS>:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:04.261Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:04.261Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:04.261Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:04.261Z | subchannel | (15) <IP_ADDRESS>:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:23:04.262Z | subchannel_refcount | (15) <IP_ADDRESS>:443 refcount 2 -> 1
D 2023-05-11T08:23:04.262Z | pick_first | TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:23:04.262Z | resolving_load_balancer | dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
D 2023-05-11T08:23:04.262Z | connectivity_state | (12) dns:aws.upgradingdave.com:443 TRANSIENT_FAILURE -> IDLE
10:23:05.629 | zeebe |  INFO: Set Grpc Channel state to failed after 3000ms
^CINFO app:main initating close of main window
INFO app:main asking client to allow quit
INFO app:workspace saving
INFO app:main quit allowed
INFO app:main initating close of main window
INFO app:main main window closed
dave@Davids-MBP MacOS % clear
dave@Davids-MBP MacOS % export ZEEBE_NODE_LOG_LEVEL=DEBUG GRPC_VERBOSITY=DEBUG GRPC_TRACE=all
dave@Davids-MBP MacOS % ./Camunda\ Modeler
D 2023-05-11T08:23:18.029Z | index | Loading @grpc/grpc-js version 1.8.7
INFO app:main:bootstrap starting Camunda Modeler v5.10.0
INFO app:cli parsing [ '/Applications/Camunda Modeler.app/Contents/MacOS/Camunda Modeler' ] in '/Applications/Camunda Modeler.app/Contents/MacOS'
INFO app:flags searching for flags.json in paths [
  '/Applications/Camunda Modeler.app/Contents/MacOS/resources',
  '/Users/dave/Library/Application Support/camunda-modeler/resources'
]
INFO app:flags found [
  '/Users/dave/Library/Application Support/camunda-modeler/resources/flags.json'
]
INFO app:flags active { 'zeebe-ssl-certificate': '/Users/dave/.ssh/tls.pem' }
INFO app:error-tracking Sentry initialized.
INFO app:plugins searching for plugins/*/index.js in paths [
  '/Applications/Camunda Modeler.app/Contents/MacOS',
  '/Applications/Camunda Modeler.app/Contents/MacOS/resources',
  '/Users/dave/Library/Application Support/camunda-modeler/resources',
  '/Users/dave/Library/Application Support/camunda-modeler'
]
INFO app:plugins found plug-in entries []
INFO app:plugins registered []
INFO app:main:bootstrap received ready
objc[63836]: Class WebSwapCGLLayer is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/Frameworks/libANGLE-shared.dylib (0x7ffb4c9ccec8) and /Applications/Camunda Modeler.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/libGLESv2.dylib (0x1126a3228). One of the two will be used. Which one is undefined.
INFO app:workspace restoring /Users/dave/code/camunda-8-helm-profiles/bpmn/simple_sendgrid.bpmn
INFO app:workspace restoring /Users/dave/code/camunda-8-helm-profiles/bpmn/BenchmarkProcess.bpmn
INFO app:workspace restoring /Users/dave/code/camunda-8-helm-profiles/bpmn/simple_inbound_connector.bpmn
INFO app:main window focused
INFO app:main:bootstrap received client-ready
INFO app:workspace saving
INFO app:main window focused
ERROR app:zeebe-api Failed to read custom SSL certificate: Error: ENOENT: no such file or directory, open '/Users/dave/.ssh/tls.pem'
    at Object.openSync (node:fs:594:3)
    at Object.func [as openSync] (node:electron/js2c/asar_bundle:2:1822)
    at Object.readFileSync (node:fs:462:35)
    at t.readFileSync (node:electron/js2c/asar_bundle:2:9165)
    at module.exports.readFile (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/file-system.js:58:38)
    at ZeebeAPI._readRootCertificate (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/zeebe-api/zeebe-api.js:352:23)
    at ZeebeAPI._withTLSConfig (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/zeebe-api/zeebe-api.js:321:25)
    at ZeebeAPI._createZeebeClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/zeebe-api/zeebe-api.js:304:26)
    at ZeebeAPI._getZeebeClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/zeebe-api/zeebe-api.js:255:36)
    at ZeebeAPI.checkConnection (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/lib/zeebe-api/zeebe-api.js:108:31) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/Users/dave/.ssh/tls.pem'
}
INFO app:workspace saving
10:23:27.205 | zeebe |  INFO: Grpc Middleware blocking: false
D 2023-05-11T08:23:27.551Z | resolving_load_balancer | dns:localhost:26500 IDLE -> IDLE
D 2023-05-11T08:23:27.553Z | connectivity_state | (1) dns:localhost:26500 IDLE -> IDLE
D 2023-05-11T08:23:27.553Z | dns_resolver | Resolver constructed for target dns:localhost:26500
D 2023-05-11T08:23:27.555Z | channel | (1) dns:localhost:26500 Channel constructed with options {
  "grpc.enable_retries": 1,
  "grpc.initial_reconnect_backoff_ms": 1000,
  "grpc.max_reconnect_backoff_ms": 10000,
  "grpc.min_reconnect_backoff_ms": 5000,
  "grpc.keepalive_time_ms": 180000,
  "grpc.keepalive_timeout_ms": 120000,
  "grpc.http2.min_time_between_pings_ms": 90000,
  "grpc.http2.min_ping_interval_without_data_ms": 90000,
  "grpc.keepalive_permit_without_calls": 1,
  "grpc.http2.max_pings_without_data": 0
}
D 2023-05-11T08:23:27.556Z | channel_stacktrace | (1) Channel constructed
    at new InternalChannel (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/internal-channel.js:196:23)
    at new ChannelImplementation (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/channel.js:35:32)
    at new Client (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/client.js:65:36)
    at new ServiceClientImpl (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/@grpc/grpc-js/build/src/make-client.js:58:5)
    at new GrpcClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcClient.js:127:23)
    at GrpcMiddleware.createInterceptedGrpcClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcMiddleware.js:42:28)
    at new GrpcMiddleware (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/GrpcMiddleware.js:39:32)
    at ConnectionFactory.getGrpcClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/lib/ConnectionFactory.js:20:28)
    at ZBClient.constructGrpcClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/zb/ZBClient.js:938:75)
    at new ZBClient (/Applications/Camunda Modeler.app/Contents/Resources/app.asar/node_modules/zeebe-node/dist/zb/ZBClient.js:130:42)
D 2023-05-11T08:23:27.558Z | channel | (1) dns:localhost:26500 createResolvingCall [0] method="/gateway_protocol.Gateway/Topology", deadline=Infinity
D 2023-05-11T08:23:27.558Z | resolving_call | [0] Created
D 2023-05-11T08:23:27.558Z | resolving_call | [0] Deadline: Infinity
D 2023-05-11T08:23:27.558Z | resolving_call | [0] start called
D 2023-05-11T08:23:27.559Z | dns_resolver | Looking up DNS hostname localhost
D 2023-05-11T08:23:27.561Z | resolving_load_balancer | dns:localhost:26500 IDLE -> CONNECTING
D 2023-05-11T08:23:27.561Z | connectivity_state | (1) dns:localhost:26500 IDLE -> CONNECTING
D 2023-05-11T08:23:27.561Z | channel | (1) dns:localhost:26500 callRefTimer.ref | configSelectionQueue.length=1 pickQueue.length=0
D 2023-05-11T08:23:27.561Z | resolving_call | [0] startRead called
D 2023-05-11T08:23:27.565Z | resolving_call | [0] write() called with message of length 0
D 2023-05-11T08:23:27.565Z | resolving_call | [0] halfClose called
D 2023-05-11T08:23:27.583Z | dns_resolver | Resolved addresses for target dns:localhost:26500: [::1:26500,<IP_ADDRESS>:26500]
D 2023-05-11T08:23:27.585Z | pick_first | Connect to address list ::1:26500,<IP_ADDRESS>:26500
D 2023-05-11T08:23:27.586Z | subchannel | (2) ::1:26500 Subchannel constructed with options {
  "grpc.enable_retries": 1,
  "grpc.initial_reconnect_backoff_ms": 1000,
  "grpc.max_reconnect_backoff_ms": 10000,
  "grpc.min_reconnect_backoff_ms": 5000,
  "grpc.keepalive_time_ms": 180000,
  "grpc.keepalive_timeout_ms": 120000,
  "grpc.http2.min_time_between_pings_ms": 90000,
  "grpc.http2.min_ping_interval_without_data_ms": 90000,
  "grpc.keepalive_permit_without_calls": 1,
  "grpc.http2.max_pings_without_data": 0
}
D 2023-05-11T08:23:27.586Z | subchannel_refcount | (2) ::1:26500 refcount 0 -> 1
D 2023-05-11T08:23:27.586Z | subchannel | (3) <IP_ADDRESS>:26500 Subchannel constructed with options {
  "grpc.enable_retries": 1,
  "grpc.initial_reconnect_backoff_ms": 1000,
  "grpc.max_reconnect_backoff_ms": 10000,
  "grpc.min_reconnect_backoff_ms": 5000,
  "grpc.keepalive_time_ms": 180000,
  "grpc.keepalive_timeout_ms": 120000,
  "grpc.http2.min_time_between_pings_ms": 90000,
  "grpc.http2.min_ping_interval_without_data_ms": 90000,
  "grpc.keepalive_permit_without_calls": 1,
  "grpc.http2.max_pings_without_data": 0
}
D 2023-05-11T08:23:27.587Z | subchannel_refcount | (3) <IP_ADDRESS>:26500 refcount 0 -> 1
D 2023-05-11T08:23:27.587Z | subchannel_refcount | (2) ::1:26500 refcount 1 -> 2
D 2023-05-11T08:23:27.587Z | subchannel_refcount | (3) <IP_ADDRESS>:26500 refcount 1 -> 2
D 2023-05-11T08:23:27.587Z | pick_first | Start connecting to subchannel with address ::1:26500
D 2023-05-11T08:23:27.587Z | pick_first | IDLE -> CONNECTING
D 2023-05-11T08:23:27.587Z | resolving_load_balancer | dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.587Z | channel | (1) dns:localhost:26500 callRefTimer.unref | configSelectionQueue.length=1 pickQueue.length=0
D 2023-05-11T08:23:27.588Z | connectivity_state | (1) dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.589Z | subchannel | (2) ::1:26500 IDLE -> CONNECTING
D 2023-05-11T08:23:27.589Z | pick_first | CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.589Z | resolving_load_balancer | dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.589Z | connectivity_state | (1) dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.590Z | subchannel | (3) <IP_ADDRESS>:26500 IDLE -> CONNECTING
D 2023-05-11T08:23:27.591Z | pick_first | CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.591Z | resolving_load_balancer | dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.591Z | connectivity_state | (1) dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.610Z | channel | (1) dns:localhost:26500 createRetryingCall [1] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:23:27.612Z | retrying_call | [1] start called
D 2023-05-11T08:23:27.612Z | channel | (1) dns:localhost:26500 createLoadBalancingCall [2] method="/gateway_protocol.Gateway/Topology"
D 2023-05-11T08:23:27.612Z | retrying_call | [1] Created child call [2] for attempt 1
D 2023-05-11T08:23:27.613Z | load_balancing_call | [2] start called
D 2023-05-11T08:23:27.613Z | load_balancing_call | [2] Pick result: QUEUE subchannel: null status: undefined undefined
D 2023-05-11T08:23:27.613Z | channel | (1) dns:localhost:26500 callRefTimer.ref | configSelectionQueue.length=0 pickQueue.length=1
D 2023-05-11T08:23:27.613Z | retrying_call | [1] startRead called
D 2023-05-11T08:23:27.613Z | load_balancing_call | [2] startRead called
D 2023-05-11T08:23:27.614Z | retrying_call | [1] write() called with message of length 5
D 2023-05-11T08:23:27.614Z | load_balancing_call | [2] write() called with message of length 5
D 2023-05-11T08:23:27.614Z | retrying_call | [1] halfClose called
D 2023-05-11T08:23:27.648Z | subchannel | (2) ::1:26500 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:27.650Z | pick_first | CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.650Z | resolving_load_balancer | dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.650Z | channel | (1) dns:localhost:26500 callRefTimer.unref | configSelectionQueue.length=0 pickQueue.length=0
D 2023-05-11T08:23:27.650Z | load_balancing_call | [2] Pick result: QUEUE subchannel: null status: undefined undefined
D 2023-05-11T08:23:27.650Z | channel | (1) dns:localhost:26500 callRefTimer.ref | configSelectionQueue.length=0 pickQueue.length=1
D 2023-05-11T08:23:27.650Z | connectivity_state | (1) dns:localhost:26500 CONNECTING -> CONNECTING
D 2023-05-11T08:23:27.651Z | subchannel | (3) <IP_ADDRESS>:26500 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:27.651Z | pick_first | CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:27.651Z | resolving_load_balancer | dns:localhost:26500 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:27.651Z | channel | (1) dns:localhost:26500 callRefTimer.unref | configSelectionQueue.length=0 pickQueue.length=0
D 2023-05-11T08:23:27.651Z | load_balancing_call | [2] Pick result: TRANSIENT_FAILURE subchannel: null status: 14 No connection established
D 2023-05-11T08:23:27.651Z | load_balancing_call | [2] ended with status: code=14 details="No connection established"
D 2023-05-11T08:23:27.651Z | retrying_call | [1] Received status from child [2]
D 2023-05-11T08:23:27.651Z | retrying_call | [1] state=TRANSPARENT_ONLY handling status with progress PROCESSED from child [2] in state ACTIVE
D 2023-05-11T08:23:27.651Z | retrying_call | [1] ended with status: code=14 details="No connection established"
D 2023-05-11T08:23:27.652Z | connectivity_state | (1) dns:localhost:26500 CONNECTING -> TRANSIENT_FAILURE
D 2023-05-11T08:23:27.652Z | resolving_call | [0] ended with status: code=14 details="No connection established"

Problem solved! Thanks again for looking into this (and sorry for the trouble!)
I had the Letsencrypt staging Certificate Authorities installed in my keychain. Apparently, the staging CA certs prevent legitimate production certs from validating.
I removed the staging letsencrypt CA certs from my key chain, and now I'm able to deploy from Desktop Modeler.


1.51.0-linux-amd64 rapidly consumes memory and does not complete

Environment details

Programming language: N/A
OS: Linux (Debian 11)
Language runtime version: N/A
Package version: 1.51.0-linux-amd64

Steps to reproduce

Run api-linter

Worked fine using 1.47.0. I killed it when it hit 8 GiB.

Can also reproduce on 1.50.0.

1.48.0 appears to be the last working release.

Not sure if this is still an issue or not. We are well passed the problem release at this point. A reproduction would be useful if it is still an issue, but I will close for now unless it comes back.


Package list auto-gen request: fix links without text

Recent builds are giving these warnings in azure-dev-docs-rpr. Looks like there's just some missing text in the source spreadsheet.
articles/includes/python-all.md
Line 32, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://pypi.org/project/azure-digitaltwins-core/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 119, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://pypi.org/project/azure-mgmt-containerregistry/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 119, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerregistry_2.8.0/azure-mgmt-containerregistry/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.
articles/includes/python-new.md
Line 32, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://pypi.org/project/azure-digitaltwins-core/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 119, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://pypi.org/project/azure-mgmt-containerregistry/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.
Line 119, Column 1: [Suggestion-link-text-missing] Missing link text for link 'https://github.com/Azure/azure-sdk-for-python/tree/azure-mgmt-containerregistry_2.8.0/azure-mgmt-containerregistry/'. Add appropriate text. NOTE: This Suggestion will become a Warning on 1/29/21.

Fixed with #2060


before not working correctly - error in generated sql statement

I have a repo with the small example here: https://github.com/richardwardza/prisma-before-bug
Bug description
When using the before parameter in a findMany query, the response is not what it expected.
I have 12 clients in the table (a to l) and am paginating them 2 at a time using first: 2 and after: X (x is the last client in the previous query).
Going "forward" works fine but going "backwards" using before: X and orderBy: { id: "desc" } does not work correctly.
Forward query: await prisma.client.findMany({ first: 2, after: { id: 'b' } }); // implicit orderBy: { id: "asc" }});
Backwards query: await prisma.client.findMany({first: 2,before: { id: 'e' },orderBy: { id: "desc" }});
The generated sql for the before query looks as follows:
SELECT
"play"."Client"."id",
"play"."Client"."name"
FROM
"play"."Client"
WHERE
(
    1 = 1
    AND (
        (
            ( "play"."Client"."id" ) = ( SELECT "play"."Client"."id" FROM "play"."Client" WHERE ( "play"."Client"."id" ) = ( 'e' ) )
            AND ( "play"."Client"."id" ) < ( 'e' )
        )
        OR ( "play"."Client"."id" ) > ( SELECT "play"."Client"."id" FROM "play"."Client" WHERE ( "play"."Client"."id" ) = ( 'e' ) )
    )
)
ORDER BY
"play"."Client"."id" DESC
LIMIT 3 OFFSET 0;

The issue appears to be in the last OR:
OR ( "play"."Client"."id" ) > ( SELECT "play"."Client"."id" FROM "play"."Client" WHERE ( "play"."Client"."id" ) = ( 'e' ) )
Changing the comparison from > to < gets the correct answer back, like so:
OR ( "play"."Client"."id" ) < ( SELECT "play"."Client"."id" FROM "play"."Client" WHERE ( "play"."Client"."id" ) = ( 'e' ) )
This results in the query correctly returning:
d
c
b

How to reproduce

clone https://github.com/richardwardza/prisma-before-bug
run yarn
create a valid prisma/.env file
run yarn save
run yarn up
run yarn gen
run yarn start

Expected behavior
The output currently has:
Remove all data.
Clients created.
Retrieve first set of 2 (from start):
a
b
Retrieve second set of 2 (from after b):
c
d
Retrieve third set of 2 (from after d):
e
f
Retrieve second set of 2 (from before e):
l
k
Done

The last piece of output should be:
Retrieve second set of 2 (from before e):
d
c

Prisma information
datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

generator client {
  provider = "prisma-client-js"
}

model Client {
  id   String @default(cuid()) @id
  name String
}

Environment & setup

OS: Mac OS
Database: PostgreSQL
Prisma version: 2.0.0-beta.5
Node.js version: v12.16.1

This isn't a bug - I'm not using the findMany correctly.
The last, "backwards" query, should be:
await prisma.client.findMany({last: 2,before: { id: 'e' },orderBy: { id: "desc" }});

I'm leaving this all here but closing the ticket.
Thank you.

Thanks for the write up anyways @richardwardza
Feel to open more issues if you encounter any other problem


Cytoscape export design in any Image format tag set don't get rendered

When I export a cytoscape design the image won't have bubble set inside them it's just don't get rendered
To Reproduce

Expected behavior

Screenshots

Context

Version:
Browser:

Additional context

which version of

the bubblesets plugin
https://github.com/sgratzl/cytoscape.js-layers
are you using?


[CARBONDATA-2748] blocking concurrent load if any column included as dictionary

[x] Any interfaces changed? No

[x] Any backward compatibility impacted? No

[x] Document update required? No

[x] Testing done =>  UT added

[x] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.  NA

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7233/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6006/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7239/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6012/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7282/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6049/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7285/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7293/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6060/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5911/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7296/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5914/

retest sdv please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7301/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6068/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7308/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6075/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/6090/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7328/

LGTM
Build failed due to CI server problem

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5922/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/5930/


Mouse click not detected, but touch screen touch is

When attempting to sort items, mouse click drags do not seem to be detected when using Chrome, but touch screen drags are. Have tested without extensions and in incognito mode.

The issue I found was when the you click in the box and not on the text.  You must click on the text to drag.

It happens only in Chrome for me as well, problem is when you have click event like "X" (close card)in http://a5hik.github.io/ng-sortable/#/sprint
the event is not fired sometimes in chrome. Firefox and IE are fine.

This happens only on touch screens
ipad/safari
chrome

This is affecting me since commit 453988fbe7a86d0570bbb5e4f755e591da6560bc
When I disable touchscreen and restart browser, mouse dragging works again (I'm using Chrome 49)

@maveric1977 can you have a look in to this.. #275

@a5hik I'll check it out tonight

@a5hik I can confirm that both the simple and advanced demo pages do not drag with my mouse click in Chrome (49.0.2623.87 m), only touchscreen dragging works.
I tested the same pages in MS Edge and both work with mouse and touch.

@a5hik , @timothylippiatt : Just checked the demo page using the latest version of Google Chrome (49.0.2623.87 m) and everything works fine. I cannot reproduce the problem.

I can confirm this issue in Chrome, when using a mouse on a touch-screen laptop.


Update Webpack 3.12 to Error 4 and above.

installed webpack 4

Error;

can you paste your package.json file? especially the dependency and dev-dependency sections?

can you paste your package.json file? especially the dependency and dev-dependency sections?

Yes, of course.
{
"name": "app",
"version": "0.0.0",
"author": "Kaayo",
"description": "Protótipo",
"license": "",
"main": "./dist/electron/main.js",
"scripts": {
"build": "node .electron-vue/build.js && electron-builder",
"build:dir": "node .electron-vue/build.js && electron-builder --dir",
"build:clean": "cross-env BUILD_TARGET=clean node .electron-vue/build.js",
"build:web": "cross-env BUILD_TARGET=web node .electron-vue/build.js",
"dev": "node .electron-vue/dev-runner.js",
"watch": "cross-env BUILD_TARGET=web node .electron-vue/dev-runner.js",
"pack": "npm run pack:main && npm run pack:renderer",
"pack:main": "cross-env NODE_ENV=production webpack --progress --colors --config .electron-vue/webpack.main.config.js",
"pack:renderer": "cross-env NODE_ENV=production webpack --progress --colors --config .electron-vue/webpack.renderer.config.js",
"postinstall": ""
},
"build": {
"productName": "App",
"appId": "org.simulatedgreg.electron-vue",
"directories": {
"output": "build"
},
"files": [
"dist/electron/**/*"
],
"dmg": {
"contents": [
{
"x": 410,
"y": 150,
"type": "link",
"path": "/Applications"
},
{
"x": 130,
"y": 150,
"type": "file"
}
]
},
"mac": {
"icon": "build/icons/icon.icns"
},
"win": {
"icon": "build/icons/icon.ico"
},
"linux": {
"icon": "build/icons"
}
},
"dependencies": {
"electron-remote": "^1.3.0",
"moment": "^2.24.0",
"pg": "^7.4.3",
"ws": "^6.1.0"
},
"devDependencies": {
"@mdi/font": "^2.4.85",
"@types/moment": "^2.13.0",
"acrobat": "^0.1.0",
"ajv": "^6.10.0",
"ajv-keywords": "^3.4.0",
"babel-core": "^6.25.0",
"babel-loader": "^7.1.1",
"babel-plugin-transform-runtime": "^6.23.0",
"babel-preset-env": "^1.6.0",
"babel-preset-stage-0": "^6.24.1",
"babel-register": "^6.24.1",
"babili-webpack-plugin": "^0.1.2",
"cfonts": "^1.1.3",
"chalk": "^2.1.0",
"copy-webpack-plugin": "^4.0.1",
"cross-env": "^5.0.5",
"css-loader": "^0.28.4",
"del": "^3.0.0",
"devtron": "^1.4.0",
"electron": "^5.0.0",
"electron-builder": "^20.40.2",
"electron-debug": "^1.5.0",
"electron-devtools-installer": "^2.2.0",
"extract-text-webpack-plugin": "^3.0.0",
"file-loader": "^0.11.2",
"html-webpack-plugin": "^2.30.1",
"jest-worker": "^24.6.0",
"material-design-icons-iconfont": "^3.0.3",
"multispinner": "^0.2.1",
"node-loader": "^0.6.0",
"node-worker-farm": "^1.3.1",
"pdfmake": "^0.1.53",
"style-loader": "^0.18.2",
"stylus": "^0.54.5",
"stylus-loader": "^3.0.1",
"url-loader": "^1.0.1",
"vue": "^2.6.8",
"vue-html-loader": "^1.2.4",
"vue-loader": "^13.0.5",
"vue-router": "^3.0.1",
"vue-style-loader": "^3.0.1",
"vue-template-compiler": "^2.6.8",
"vuetify": "^1.5.5",
"vuex": "^3.1.0",
"webpack": "^3.12.0",
"webpack-dev-server": "^2.7.1",
"webpack-hot-middleware": "^2.18.2",
"worker-loader": "^2.0.0",
"worker-plugin": "^3.1.0",
"workerpool": "^3.1.2"
}
}

may I ask how did you create your app? cause I just created a new fresh app, and the webpack version was "webpack": "^4.15.1" not "webpack": "^3.12.0".
this is an example of the package.json file for the newly created project I mentioned:
{
  "name": "testing",
  "version": "0.0.1",
  "author": "Zaher Ghaibeh<EMAIL_ADDRESS>  "description": "An electron-vue project",
  "license": null,
  "main": "./dist/electron/main.js",
  "scripts": {
    "build": "node .electron-vue/build.js && electron-builder",
    "build:dir": "node .electron-vue/build.js && electron-builder --dir",
    "build:clean": "cross-env BUILD_TARGET=clean node .electron-vue/build.js",
    "build:web": "cross-env BUILD_TARGET=web node .electron-vue/build.js",
    "dev": "node .electron-vue/dev-runner.js",
    "e2e": "npm run pack && mocha test/e2e",
    "lint": "eslint --ext .js,.vue -f ./node_modules/eslint-friendly-formatter src test",
    "lint:fix": "eslint --ext .js,.vue -f ./node_modules/eslint-friendly-formatter --fix src test",
    "pack": "npm run pack:main && npm run pack:renderer",
    "pack:main": "cross-env NODE_ENV=production webpack --progress --colors --config .electron-vue/webpack.main.config.js",
    "pack:renderer": "cross-env NODE_ENV=production webpack --progress --colors --config .electron-vue/webpack.renderer.config.js",
    "test": "npm run unit && npm run e2e",
    "unit": "karma start test/unit/karma.conf.js",
    "postinstall": "npm run lint:fix"
  },
  "build": {
    "productName": "testing",
    "appId": "com.example.yourapp",
    "directories": {
      "output": "build"
    },
    "files": [
      "dist/electron/**/*"
    ],
    "dmg": {
      "contents": [
        {
          "x": 410,
          "y": 150,
          "type": "link",
          "path": "/Applications"
        },
        {
          "x": 130,
          "y": 150,
          "type": "file"
        }
      ]
    },
    "mac": {
      "icon": "build/icons/icon.icns"
    },
    "win": {
      "icon": "build/icons/icon.ico"
    },
    "linux": {
      "icon": "build/icons"
    }
  },
  "dependencies": {
    "vue": "^2.5.16",
    "axios": "^0.18.0",
    "vue-electron": "^1.0.6",
    "vue-router": "^3.0.1",
    "vuex": "^3.0.1",
    "vuex-electron": "^1.0.0"
  },
  "devDependencies": {
    "ajv": "^6.5.0",
    "babel-core": "^6.26.3",
    "babel-loader": "^7.1.4",
    "babel-plugin-transform-runtime": "^6.23.0",
    "babel-preset-env": "^1.7.0",
    "babel-preset-stage-0": "^6.24.1",
    "babel-register": "^6.26.0",
    "babili-webpack-plugin": "^0.1.2",
    "cfonts": "^2.1.2",
    "chalk": "^2.4.1",
    "copy-webpack-plugin": "^4.5.1",
    "cross-env": "^5.1.6",
    "css-loader": "^0.28.11",
    "del": "^3.0.0",
    "devtron": "^1.4.0",
    "electron": "^2.0.4",
    "electron-debug": "^1.5.0",
    "electron-devtools-installer": "^2.2.4",
    "electron-builder": "^20.19.2",
    "babel-eslint": "^8.2.3",
    "eslint": "^4.19.1",
    "eslint-friendly-formatter": "^4.0.1",
    "eslint-loader": "^2.0.0",
    "eslint-plugin-html": "^4.0.3",
    "eslint-config-standard": "^11.0.0",
    "eslint-plugin-import": "^2.12.0",
    "eslint-plugin-node": "^6.0.1",
    "eslint-plugin-promise": "^3.8.0",
    "eslint-plugin-standard": "^3.1.0",
    "mini-css-extract-plugin": "0.4.0",
    "file-loader": "^1.1.11",
    "html-webpack-plugin": "^3.2.0",
    "inject-loader": "^4.0.1",
    "karma": "^2.0.2",
    "karma-chai": "^0.1.0",
    "karma-coverage": "^1.1.2",
    "karma-electron": "^6.0.0",
    "karma-mocha": "^1.3.0",
    "karma-sourcemap-loader": "^0.3.7",
    "karma-spec-reporter": "^0.0.32",
    "karma-webpack": "^3.0.0",
    "require-dir": "^1.0.0",
    "spectron": "^3.8.0",
    "babel-plugin-istanbul": "^4.1.6",
    "chai": "^4.1.2",
    "mocha": "^5.2.0",
    "multispinner": "^0.2.1",
    "node-loader": "^0.6.0",
    "node-sass": "^4.9.2",
    "sass-loader": "^7.0.3",
    "style-loader": "^0.21.0",
    "url-loader": "^1.0.1",
    "vue-html-loader": "^1.2.4",
    "vue-loader": "^15.2.4",
    "vue-style-loader": "^4.1.0",
    "vue-template-compiler": "^2.5.16",
    "webpack-cli": "^3.0.8",
    "webpack": "^4.15.1",
    "webpack-dev-server": "^3.1.4",
    "webpack-hot-middleware": "^2.22.2",
    "webpack-merge": "^4.1.3"
  }
}

What happens is that I downloaded this boilerplate a while ago, and at the time I was already with this version of the webpack. So I'll do as you mentioned, I'll get an app from the beginning with the updated boilerplate. As soon as I do some tests here, I'll let you know. So far thank you!

I checked my boilerplate again and made a mistake, I'm using the boilerplate rolandalla / Electron-VueJs-Vuetify. I've already opened a question for the repository author.
Sorry for the mistake and thank you for the attention!
Link:  https://github.com/rolandalla/Electron-VueJs-Vuetify/issues/1

You are most welcome @Kaa10, I think you can close this issue.


Bump up to 4.8 operator SDK.

fixes: https://github.com/kiali/kiali/issues/4094
backport PR: https://github.com/kiali/kiali-operator/pull/375
Note that while we can move our images to 4.9, we cannot introduce any code that uses anything not also backward compatible with 4.7 because any downstream builds are still going to be on 4.7 (that's the latest downstream version we have available as of today).
I'm going to only bump to 4.8. since that is most likely going to be the next downstream build that will be available. Seems better to remain as close as possible. No sense jumping 2 minor versions here.
I also question if we even should do this now. Since downstream is still only at 4.7, we might want to hold off on merging this until downstream has 4.8. I will leave this as a "draft" PR because of this.

molecule tests on minikube all pass:
              accessible-namespaces-test... success [4m 1s]
     affinity-tolerations-resources-test... success [3m 56s]
                                api-test... success [3m 31s]
                      config-values-test... success [3m 26s]
                  default-namespace-test... success [2m 23s]
                        header-auth-test... success [2m 1s]
                      instance-name-test... success [2m 58s]
                            metrics-test... success [4m 48s]
                     null-cr-values-test... success [2m 11s]
                only-view-only-mode-test... success [2m 56s]
                             openid-test... success [2m 12s]
                     openshift-auth-test... skipped
                   os-console-links-test... skipped
                              roles-test... success [5m 7s]
                    rolling-restart-test... success [2m 59s]
                              token-test... success [2m 16s]

tests on openshift 4.7 are ok.

I'm going to change from 4.9 to 4.8. The weird thing is, nothing changes between those two base images - the ansible operator sdk is still 1.8.0 and the kubernetes collections is still 1.2. And we have to use "4.8' not "4.8.0" because the .0 versions are all old. I have a feeling something isn't right with the ansible operator builds that are released. But for now, we will use 4.8.

molecule tests all pass with 4.8, too.

Note that this PR also enables metadata validation checks for the latest bundles - this should be independent of the version bump. I may rip that out and put it into a separate PR because I'm not convinced we should be moving to 4.8 now (considering the downstream version doesn't have 4.8 yet).

This is ready for review. Moved to v4.8. This also moves all usages of the k8s plugin to community.kubernetes.k8s (with the intention that in the future, when the base image moves, we move to kubernetes.core with it).

I am going to run the molecule tests. Once confirmed, I'll backport this PR to v1.36.

molecule testing looks ok. backport PR created. Ready for merge


Several links error in README.md.

System information

OS: Windows 10 Enterprise x64:
Browser: Chrome 58 x64:
Location: China:

Issue
The Installing TensorFlow link from README.md fails with error:
Error: Not Found

The requested URL /versions/r0.12/install/index.html was not found on this server.

The Community link fails with error:
Error: Not Found

The requested URL /versions/r0.12/community/index.html was not found on this server.

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Please also include more information on what commands you ran to produce the output. Thanks!

@skye Thanks for reply. I know it's not a product bug, but it's a doc bug. The README.md doc has several invalid site links, i don't think this should be asked in StackOverflow.

Ah sorry, didn't read the issue closely enough!

Hm, the "Installing Tensorflow" link at https://github.com/tensorflow/tensorflow goes to https://www.tensorflow.org/install/, and the "Community" link goes to https://www.tensorflow.org/community/. Am I missing something?

Yes, you are right. But the two links redirect to invalid sites with a "404 Not Found" result.
https://www.tensorflow.org/install/ redirects to
https://www.tensorflow.org/versions/r0.12/install/index.html
and https://www.tensorflow.org/community/ redirects to https://www.tensorflow.org/versions/r0.12/community/index.html
btw: I'm in China, hope this helps.

@dr4b does this ring any bells for you? (See the above comment.) Those links don't redirect for me, but I'm not sure if being in China should affect this.

It seems like you might be accessing an old version of the site somehow. I'll ping our infrastructure team to see if they can look into this. In the meantime, if you have access to the github, you can look at the docs source directly:
Installation page: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/docs_src/install/index.md
Community page: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/docs_src/community/index.md
All the non-API pages should be in that docs_src directory, and the documentation for individual API methods, classes, etc. is generated from the docstrings in the source files. Let me know if you need help finding something.

@skye Thanks.


flag klog.V(0) and logger.V(0)

Calling V with zero as parameter just causes additional overhead.

/assign

/remove-lifecycle stale
/triage accepted

I think we are done with this issue - probably already should have closed it a while ago...
/close


Refactor search filter code

Move all search filter from being string based with a prefix, to an object holding current filters.

Manual testing of the discover page reviews a few oddities. We're going to roll this into another PR for now, but can you please follow up?
Most of these comments refer to initial load of page. Sometimes buttons start working after I take other actions (like sorting).

The "refine your search" items look like checkboxes, but (mostly) act like radio buttons that only allow one selection at a time. This is slightly confusing.
If I click "clear filters", the labels are on the same line.
If I try to select a subject filter, the checkbox does nothing. (clickable but not selected) In the console, I see discover.js:267 Uncaught TypeError: Cannot read property 'filter' of undefined
Why does the subject tree show an expand icon next to things with no children? If I try to expand, I get discover.js:27 Uncaught TypeError: Cannot read property 'slice' of undefined

Also: clicking "clear filters" does not clear subject filters.

Once all filters are cleared, I can no longer see search results. (even though I had them when I first loaded the page). My console froze up, but at some point I got this error message which might be helpful:
discover.js:137 Uncaught TypeError: Cannot read property 'indexOf' of undefined

Sorry for the notes, but hope these examples and error message links help you trace things a bit.

Lastly, any idea why we get all these "rerender" warnings? I;m noticing some sluggish page behavior, and ember might be trying to warn us about... something?

Rolled into #45, but requesting author create tickets to follow up on outstanding issues with the page.


[stable/elasticsearch-exporter] Add imagePullSecret support

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

This PR adds support for using an image pull secret.

/assign @svenmueller

/approve

Is there anything required from side to get this in?

/assign
/ok-to-test
/lgtm
@svenmueller, also added you as a trusted collaborator so you can be assigned.


Upload to playstore finished successfully but is not uploaded

Hello,
just tried to set up the lane for uploading to playstore, but it doesn't seem to work. It says it finished sucessfully, but on my playstore console. Nothing got uploaded.
This is what i get, when I execute my lane for uploading to playstore:
PS C:\Flutter\src\hapii\android> fastlane alpha
 [✔] 🚀
[18:01:05]: fastlane detected a Gemfile in the current directory
[18:01:05]: however it seems like you don't use `bundle exec`
[18:01:05]: to launch fastlane faster, please use
[18:01:05]:
[18:01:05]: $ bundle exec fastlane alpha
[18:01:05]:
[18:01:05]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[18:01:07]: -----------------------------
[18:01:07]: --- Step: update_fastlane ---
[18:01:07]: -----------------------------
[18:01:07]: Looking for updates for fastlane...
[18:01:09]: Nothing to update ✅
[18:01:09]:
[18:01:09]: Please help us test early releases of fastlane by opting into nightly builds 🌃
[18:01:09]: Just replace your `update_fastlane` call with
[18:01:09]:
[18:01:09]: ▸ update_fastlane(nightly: true)
[18:01:09]:
[18:01:09]: Nightly builds are reviewed and tested just like the public releases 🚂
[18:01:09]:
[18:01:09]: ------------------------------
[18:01:09]: --- Step: default_platform ---
[18:01:09]: ------------------------------
[18:01:09]: Driving the lane 'alpha' 🚀
[18:01:09]: ----------------------------------
[18:01:09]: --- Step: upload_to_play_store ---
[18:01:09]: ----------------------------------

+-------------------------+------------------------------------+
|                  Summary for supply 2.108.0                  |
+-------------------------+------------------------------------+
| track                   | beta                               |
| json_key                | googleServiceAccountPlayStore.json |
| skip_upload_images      | true                               |
| package_name            | com.hapi.hapiapp                   |
| metadata_path           | ./fastlane/metadata/android        |
| skip_upload_apk         | false                              |
| skip_upload_aab         | false                              |
| skip_upload_metadata    | false                              |
| skip_upload_screenshots | false                              |
| validate_only           | false                              |
| check_superseded_tracks | false                              |
| timeout                 | 300                                |
| deactivate_on_promote   | true                               |
+-------------------------+------------------------------------+

[18:01:10]: Preparing to upload for language 'de-DE'...
[18:01:11]: Updating changelog for code version '1' and language 'de-DE'...
[18:01:12]: Uploading all changes to Google Play...
[18:01:14]: Successfully finished the upload to Google Play

+------+----------------------+-------------+
|             fastlane summary              |
+------+----------------------+-------------+
| Step | Action               | Time (in s) |
+------+----------------------+-------------+
| 1    | update_fastlane      | 2           |
| 2    | default_platform     | 0           |
| 3    | upload_to_play_store | 4           |
+------+----------------------+-------------+

[18:01:14]: fastlane.tools finished successfully 🎉

`✅ fastlane environment ✅
Stack

Key
Value

OS
UNKNOWN

Ruby
2.5.3

Bundler?
false

Git
git version 2.19.1.windows.1

Installation Source
C:/Ruby25-x64/bin/fastlane

Host
Unknown  ()

Ruby Lib Dir
C:/Ruby25-x64/lib

OpenSSL Version
OpenSSL 1.1.1  11 Sep 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
update_fastlane

default_platform(:android)

platform :android do
  desc "Runs all the tests"
  lane :test do
    gradle(task: "test")
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    gradle(task: "clean assembleRelease")
    crashlytics

    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "clean assembleRelease")
  end
end

lane :alpha do
  upload_to_play_store(
    track: 'beta',
    json_key: "googleServiceAccountPlayStore.json",
    skip_upload_images: true
  )
end

`./fastlane/Appfile`
package_name("com.hapi.hapiapp")

fastlane gems

Gem
Version
Update-Status

fastlane
2.108.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.2.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.7.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
1.8.0

unicode-display_width
1.4.0

terminal-table
1.8.0

plist
3.4.0

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-screen
0.6.5

tty-cursor
0.6.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.62.0

faraday
0.15.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.4

gh_inspector
1.1.3

json
2.1.0

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.5.0

bundler
1.16.6

faraday_middleware
0.12.2

naturally
2.2.0

simctl
1.6.5

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

addressable
2.5.2

mime-types-data
3.2018.0812

mime-types
3.2.2

jwt
2.1.0

signet
0.11.0

memoist
0.16.0

os
1.0.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

emoji_regex
0.1.1

openssl
2.1.2

fiddle
1.0.0

date
1.0.0

fileutils
1.0.2

ipaddr
1.2.0

psych
3.0.2

generated on: 2018-11-18`

@janpio Uploading via "fastlane supply" worked correctly now, my internet connection was slow. The output "Preparing apk at path" is little bit missunderstanding, because it is not preparing it is uploading.
But uploading via the fastlane script with the function "upload_to_play_store" is still not working correctly. The output says that the command "fastlane alpha" finished successfully. But no apk is uploaded and as you see in the output the function "upload_to_play_store" takes 4s. 4s are to less to upload the apk. This i proved also in the play store developer console. Apk is not uploaded via the "fastlane alpha" command.

4s are more than enough for what you ask upload_to_play_store to do:
fastlane alpha is a command that executes the alpha lane (from your Fastfile):
lane :alpha do
  upload_to_play_store(
    track: 'beta',
    json_key: "googleServiceAccountPlayStore.json",
    skip_upload_images: true
  )
end

You are missing the path to the APK here, so it is just uploading and updating the metadata.
This will probably work just fine as it is if you run a lane that executes gradle right before, as this will set an environment variable with the APK path, and it will appear in the Summary for supply ... table. But to make sure this lane always works, you will have to set the the path to the apk in the apk option/parameter.

@janpio  Thanks a lot, that was the problem. Thanks!


simplify font choices

hahaha, so many different font styles hahaha

Haha yah that comes from Jekyll default + using css framework http://milligram.github.io

done


Add more math functions

Adding methods in java.lang.Math class as function.

:+1:

@navis can we get some documentation about using these math functions?

@fjy I'll append function list to math-expr.md

👍