Can't find the mentioned "FAQ-Saas-Sample"  in CF "Consumer"-Subaccount.

Hi @IObert,
I can't find the mentioned "FAQ-Saas-Sample" in my "Consumer"-Subaccount.
Any ideas?
Thanks & best Regards
Dirk

Can you confirm that you deployed all resources in the provider subaccount correctly (e.g. are all pods in state running)? And does your consumer subaccount live in the same region as the provider subaccoubt?

The only one thing, that didn't work for me before, was that I had an issue with creating the "secrets".
Everythings seems fine while creating the secrets, but as soon as I click the link sm-credentials, I see only an empty view.

{
 "clientid": "",
 "clientsecret": "",
 "sm_url": "",
 "url": "",
 "xsappname": ""
}

Maybe you know this issue...
Thanks!

I don't know the issue but this surely explains why the deployments failed and why you don't see the SaaS option in the consumer sa.
Are these values also empty in the faq-container-key.json file? If so, I recommend that you go back to the following command and run everything from there again:
cf create-service-key faq-saas-container faq-container-key
cf service-key faq-saas-container faq-container-key | tail -n +3 > faq-container-key.json

No, sorry. I removed only the values. It shows only the structure of the faq-container-key.json file.
My command is a little bit different, because I'm on Windows I had to change the command to
cf service-key faq-saas-container faq-container-key > faq-container-key.json
and removed the first three lines manually. But this shouldn't cause the issue.
I tried it today again. Same result.
this is the error msg from the Console:
react-dom.production.min.js:196 DOMException: Failed to execute 'btoa' on 'Window': The string to be encoded contains characters outside of the Latin1 range.

So you mean that you removed the values for the post here (which makes sense) but the values are part of the file?
I wouldn't focus on the UI error that you get in the Kyma console. Can you decode and read the secret with kubectl:
https://kubernetes.io/docs/tasks/configmap-secret/managing-secret-using-kubectl/#decoding-secret

I can see the sm-credentials
PS C:\git\kyma-mtx-faq-management>
kubectl get secrets --namespace project-faq
NAME                                        TYPE                                  DATA   AGE
sm-credentials                              Opaque                                1      139m
I could fetch the encoded secrets with
 kubectl get secret sm-credentials -o jsonpath='{.data.credentials}'  --namespace project-faq
But decoding with this command does work for me
echo 'MWYyZDFlMmU2N2Rm' | base64 --decode
tried also
kubectl get secret sm-credentials -o jsonpath='{.data.credentials}'  --namespace project-faq | base64 --decode --namespace project-faq
but I'm wondering because my base64 (//57AA0ACgAgACIAYwBsAGkAZQBuAHQAaQBkAC...) is starting with //
maybe I need to switch to Linux

Yes, that decoding seems to be a problem with Windows. I'm sure the Windows terminal has an equivalent command - or you could use the Git Bash to decode it
I heard that WSL works quite good but I don't expect that the the base64 encoding is causing you problem. It's probably related to the deployment.
Have a look at your Kyma namespace to see if

All deployments are running:

All pods are running (it's ok if some of them restarted once or twice)

These two service instances were created

I suspect that your service instance is missing or that the provisioning failed

Thanks!
Realized that my faq-backend fails. (there was yesterday an other msg which I wasn't able to understand)
kubectl get deployment faq-backend  --namespace project-faq
NAME          READY   UP-TO-DATE   AVAILABLE   AGE
faq-backend   0/1     1            0           2m9s

But I saw that this deployment needs the secrets SM_CREDENTIALS in the .yaml file.
So I guess that this deployment isn't able to start without the secrets and runs in this error.

Yes, that causes the problem. Can you paste the error log of the deployment (or better: the pod that belongs to the deployment) here?

tried to find out, what the command is, but wasn't able to find it

Yes, that's the place. You can click there on the three dots and select "show logs". This UI will only show you the past X minutes. But you can remove the entire pods (... -> delete) and then inspect the logs of the newly added pod.

Let me know if you need more. Thanks

<div class="fd-panel fd-has-padding-small fd-has-padding-right-regular fd-has-padding-left-regular sticky-header" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-variant-numeric: inherit; font-variant-east-asian: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; --fd-panel-background-color:var(--fd-color-background-2,#fff); --fd-panel-border-color:var(--fd-color-neutral-2,#eeeeef); --fd-panel-box-shadow-color:var(--fd-color-neutral-2,#eeeeef); --fd-panel-divider-color:var(--fd-panel-border-color,var(--fd-color-neutral-2,#eeeeef)); --fd-panel-title-color:var(--fd-color-text-1,#32363a); background-color: var(--fd-panel-background-color,#fff); box-shadow: 0 5px 20px 0 var(--fd-panel-box-shadow-color,var(--fd-color-neutral-2,#eeeeef)); --fd-panel-border-width:0; border-radius: 4px; color: rgb(50, 54, 58); -webkit-font-smoothing: antialiased; position: sticky; top: 0px; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">

Logs

<input type="text" class="search-input--compact" placeholder="Search" id="search-input" value="" style="box-sizing: border-box; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; line-height: 1.42857; font-weight: 400; appearance: textfield; font-size: inherit; outline: 0px; color: var(--fd-forms-color); border-width: 1px; border-style: solid; border-image: initial; border-color: var(--fd-forms-border-color); background-color: var(--fd-forms-background-color); border-radius: 4px; transition: border-color 125ms ease 0s; padding-left: 12px; padding-right: 12px; height: var(--fd-forms-height); width: 191.484px; display: block;">
<div class="fd-popover" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; display: inline-block;">
<div class="fd-popover__control" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; cursor: pointer;"><button tabindex="0" role="button" aria-controls="fd-jWv1S69Lb" aria-expanded="false" aria-haspopup="true" class="fd-button--light sap-icon--action-settings fd-has-margin-right-tiny" style="box-sizing: border-box; --fd-button-color:var(--fd-color-action-1,#0a6ed1); --fd-button-border-color:transparent; --fd-button-background-color:transparent; height: var(--fd-forms-height,36px); max-height: var(--fd-forms-height,36px); min-width: var(--fd-forms-height,36px); font-size: 14px; line-height: var(--fd-button-line-height,34px); color: var(--fd-button-color,#0a6ed1); border-color: var(--fd-button-border-color,transparent); border-style: solid; border-width: 1px; border-image: initial; background-color: var(--fd-button-background-color,transparent); font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; -webkit-font-smoothing: antialiased; display: inline-block; margin-top: 0px; margin-right: 8px !important; margin-bottom: 0px; margin-left: 0px; appearance: none; outline: 0px; text-decoration: none; cursor: pointer; user-select: none; vertical-align: middle; white-space: nowrap; border-radius: 4px; font-weight: 400; padding: 0px; text-align: center; transition: all 125ms ease-in 0s;"></button>

<button data-test-id="auto-refresh-button" class="fd-button--light sap-icon--media-pause link-button fd-has-margin-right-tiny fd-has-type-minus-1" style="box-sizing: border-box; --fd-button-color:var(--fd-color-action-1,#0a6ed1); --fd-button-border-color:transparent; --fd-button-background-color:transparent; height: var(--fd-forms-height,36px); max-height: var(--fd-forms-height,36px); min-width: var(--fd-forms-height,36px); font-size: 12px; line-height: 1.33333; color: var(--fd-color-action-1); border-color: var(--fd-button-border-color,transparent); border-style: solid; border-width: 1px; border-image: initial; background-color: var(--fd-button-background-color,transparent); font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; -webkit-font-smoothing: antialiased; display: inline-block; margin-top: 0px; margin-right: 8px !important; margin-bottom: 0px; margin-left: 0px; appearance: none; outline: 0px; text-decoration: none; cursor: pointer; user-select: none; vertical-align: middle; white-space: nowrap; border-radius: 4px; font-weight: 400; padding: 0px 12px; text-align: center; transition: all 125ms ease-in 0s;">auto refresh</button><div class="fd-popover" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; display: inline-block;">
<div class="fd-popover__control" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; cursor: pointer;"><button tabindex="0" role="button" aria-controls="fd-cmitIJivdz" aria-expanded="false" aria-haspopup="true" class="fd-button--light sap-icon--past fd-has-margin-right-tiny" style="box-sizing: border-box; --fd-button-color:var(--fd-color-action-1,#0a6ed1); --fd-button-border-color:transparent; --fd-button-background-color:transparent; height: var(--fd-forms-height,36px); max-height: var(--fd-forms-height,36px); min-width: var(--fd-forms-height,36px); font-size: 14px; line-height: var(--fd-button-line-height,34px); color: var(--fd-button-color,#0a6ed1); border-color: var(--fd-button-border-color,transparent); border-style: solid; border-width: 1px; border-image: initial; background-color: var(--fd-button-background-color,transparent); font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; -webkit-font-smoothing: antialiased; display: inline-block; margin-top: 0px; margin-right: 8px !important; margin-bottom: 0px; margin-left: 0px; appearance: none; outline: 0px; text-decoration: none; cursor: pointer; user-select: none; vertical-align: middle; white-space: nowrap; border-radius: 4px; font-weight: 400; padding: 0px; text-align: center; transition: all 125ms ease-in 0s;"></button>

<div class="fd-popover" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; display: inline-block;">
<div class="fd-popover__control" style="box-sizing: border-box; margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-variant: inherit; font-weight: 400; font-stretch: inherit; font-size: 14px; line-height: 1.42857; font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; vertical-align: baseline; color: var(--fd-color-text-1,#32363a); -webkit-font-smoothing: antialiased; position: relative; cursor: pointer;"><button tabindex="0" role="button" aria-controls="fd-SF9OFodQHu" aria-expanded="false" aria-haspopup="true" class="fd-button--light sap-icon--sort fd-has-margin-right-tiny" style="box-sizing: border-box; --fd-button-color:var(--fd-color-action-1,#0a6ed1); --fd-button-border-color:transparent; --fd-button-background-color:transparent; height: var(--fd-forms-height,36px); max-height: var(--fd-forms-height,36px); min-width: var(--fd-forms-height,36px); font-size: 14px; line-height: var(--fd-button-line-height,34px); color: var(--fd-button-color,#0a6ed1); border-color: var(--fd-button-border-color,transparent); border-style: solid; border-width: 1px; border-image: initial; background-color: var(--fd-button-background-color,transparent); font-family: "72", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol"; -webkit-font-smoothing: antialiased; display: inline-block; margin-top: 0px; margin-right: 8px !important; margin-bottom: 0px; margin-left: 0px; appearance: none; outline: 0px; text-decoration: none; cursor: pointer; user-select: none; vertical-align: middle; white-space: nowrap; border-radius: 4px; font-weight: 400; padding: 0px; text-align: center; transition: all 125ms ease-in 0s;"></button>

Timestamp | Log
-- | --
2021-06-01T11:14:11.407530631Z | {"log":"# Completed on Tue Jun 1 11:14:11 2021 ","time":"2021-06-01T11:14:11.407530631Z"}
2021-06-01T11:14:11.407525731Z | {"log":"COMMIT ","time":"2021-06-01T11:14:11.407525731Z"}
2021-06-01T11:14:11.407520431Z | {"log":"-A ISTIO_REDIRECT -p tcp -j REDIRECT --to-ports 15001 ","time":"2021-06-01T11:14:11.407520431Z"}
2021-06-01T11:14:11.407515831Z | {"log":"-A ISTIO_OUTPUT -j ISTIO_REDIRECT ","time":"2021-06-01T11:14:11.407515831Z"}
2021-06-01T11:14:11.407510931Z | {"log":"-A ISTIO_OUTPUT -d <IP_ADDRESS>/32 -j RETURN ","time":"2021-06-01T11:14:11.407510931Z"}
2021-06-01T11:14:11.407505631Z | {"log":"-A ISTIO_OUTPUT -m owner --gid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.407505631Z"}
2021-06-01T11:14:11.407500831Z | {"log":"-A ISTIO_OUTPUT -o lo -m owner ! --gid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.407500831Z"}
2021-06-01T11:14:11.407496131Z | {"log":"-A ISTIO_OUTPUT ! -d <IP_ADDRESS>/32 -o lo -m owner --gid-owner 1337 -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.407496131Z"}
2021-06-01T11:14:11.407491231Z | {"log":"-A ISTIO_OUTPUT -m owner --uid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.407491231Z"}
2021-06-01T11:14:11.407486731Z | {"log":"-A ISTIO_OUTPUT -o lo -m owner ! --uid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.407486731Z"}
2021-06-01T11:14:11.407481131Z | {"log":"-A ISTIO_OUTPUT ! -d <IP_ADDRESS>/32 -o lo -m owner --uid-owner 1337 -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.407481131Z"}
2021-06-01T11:14:11.407467631Z | {"log":"-A ISTIO_OUTPUT -s <IP_ADDRESS>/32 -o lo -j RETURN ","time":"2021-06-01T11:14:11.407467631Z"}
2021-06-01T11:14:11.407432531Z | {"log":"-A ISTIO_IN_REDIRECT -p tcp -j REDIRECT --to-ports 15006 ","time":"2021-06-01T11:14:11.407432531Z"}
2021-06-01T11:14:11.407427631Z | {"log":"-A ISTIO_INBOUND -p tcp -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.407427631Z"}
2021-06-01T11:14:11.407422831Z | {"log":"-A ISTIO_INBOUND -p tcp -m tcp --dport 15020 -j RETURN ","time":"2021-06-01T11:14:11.407422831Z"}
2021-06-01T11:14:11.407416831Z | {"log":"-A ISTIO_INBOUND -p tcp -m tcp --dport 15021 -j RETURN ","time":"2021-06-01T11:14:11.407416831Z"}
2021-06-01T11:14:11.407394531Z | {"log":"-A ISTIO_INBOUND -p tcp -m tcp --dport 15090 -j RETURN ","time":"2021-06-01T11:14:11.407394531Z"}
2021-06-01T11:14:11.407389331Z | {"log":"-A ISTIO_INBOUND -p tcp -m tcp --dport 22 -j RETURN ","time":"2021-06-01T11:14:11.407389331Z"}
2021-06-01T11:14:11.407384031Z | {"log":"-A ISTIO_INBOUND -p tcp -m tcp --dport 15008 -j RETURN ","time":"2021-06-01T11:14:11.407384031Z"}
2021-06-01T11:14:11.407378931Z | {"log":"-A OUTPUT -p tcp -j ISTIO_OUTPUT ","time":"2021-06-01T11:14:11.407378931Z"}
2021-06-01T11:14:11.407371031Z | {"log":"-A PREROUTING -p tcp -j ISTIO_INBOUND ","time":"2021-06-01T11:14:11.407371031Z"}
2021-06-01T11:14:11.407330931Z | {"log":":ISTIO_REDIRECT - [0:0] ","time":"2021-06-01T11:14:11.407330931Z"}
2021-06-01T11:14:11.407326331Z | {"log":":ISTIO_OUTPUT - [0:0] ","time":"2021-06-01T11:14:11.407326331Z"}
2021-06-01T11:14:11.407321531Z | {"log":":ISTIO_IN_REDIRECT - [0:0] ","time":"2021-06-01T11:14:11.407321531Z"}
2021-06-01T11:14:11.407316731Z | {"log":":ISTIO_INBOUND - [0:0] ","time":"2021-06-01T11:14:11.407316731Z"}
2021-06-01T11:14:11.407311631Z | {"log":":POSTROUTING ACCEPT [0:0] ","time":"2021-06-01T11:14:11.407311631Z"}
2021-06-01T11:14:11.407302831Z | {"log":":OUTPUT ACCEPT [0:0] ","time":"2021-06-01T11:14:11.407302831Z"}
2021-06-01T11:14:11.407266032Z | {"log":":INPUT ACCEPT [0:0] ","time":"2021-06-01T11:14:11.407266032Z"}
2021-06-01T11:14:11.407260932Z | {"log":":PREROUTING ACCEPT [0:0] ","time":"2021-06-01T11:14:11.407260932Z"}
2021-06-01T11:14:11.407249432Z | {"log":"*nat ","time":"2021-06-01T11:14:11.407249432Z"}
2021-06-01T11:14:11.407054532Z | {"log":"# Generated by iptables-save v1.6.2 on Tue Jun 1 11:14:11 2021 ","time":"2021-06-01T11:14:11.407054532Z"}
2021-06-01T11:14:11.400728456Z | {"log":"iptables-save ","time":"2021-06-01T11:14:11.400728456Z"}
2021-06-01T11:14:11.334278007Z | {"log":"ip6tables-restore --noflush /tmp/ip6tables-rules-1622546051333952108.txt586408984 ","time":"2021-06-01T11:14:11.334278007Z"}
2021-06-01T11:14:11.334272707Z | {"log":" ","time":"2021-06-01T11:14:11.334272707Z"}
2021-06-01T11:14:11.334254807Z | {"log":"Writing following contents to rules file: /tmp/ip6tables-rules-1622546051333952108.txt586408984 ","time":"2021-06-01T11:14:11.334254807Z"}
2021-06-01T11:14:11.315263378Z | {"log":"iptables-restore --noflush /tmp/iptables-rules-1622546051313506285.txt247778909 ","time":"2021-06-01T11:14:11.315263378Z"}
2021-06-01T11:14:11.315258978Z | {"log":" ","time":"2021-06-01T11:14:11.315258978Z"}
2021-06-01T11:14:11.315253778Z | {"log":"COMMIT ","time":"2021-06-01T11:14:11.315253778Z"}
2021-06-01T11:14:11.315249178Z | {"log":"-A ISTIO_OUTPUT -j ISTIO_REDIRECT ","time":"2021-06-01T11:14:11.315249178Z"}
2021-06-01T11:14:11.315244478Z | {"log":"-A ISTIO_OUTPUT -d <IP_ADDRESS>/32 -j RETURN ","time":"2021-06-01T11:14:11.315244478Z"}
2021-06-01T11:14:11.315239778Z | {"log":"-A ISTIO_OUTPUT -m owner --gid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.315239778Z"}
2021-06-01T11:14:11.315234978Z | {"log":"-A ISTIO_OUTPUT -o lo -m owner ! --gid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.315234978Z"}
2021-06-01T11:14:11.315230178Z | {"log":"-A ISTIO_OUTPUT -o lo ! -d <IP_ADDRESS>/32 -m owner --gid-owner 1337 -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.315230178Z"}
2021-06-01T11:14:11.315225278Z | {"log":"-A ISTIO_OUTPUT -m owner --uid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.315225278Z"}
2021-06-01T11:14:11.315220578Z | {"log":"-A ISTIO_OUTPUT -o lo -m owner ! --uid-owner 1337 -j RETURN ","time":"2021-06-01T11:14:11.315220578Z"}
2021-06-01T11:14:11.315215778Z | {"log":"-A ISTIO_OUTPUT -o lo ! -d <IP_ADDRESS>/32 -m owner --uid-owner 1337 -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.315215778Z"}
2021-06-01T11:14:11.315210878Z | {"log":"-A ISTIO_OUTPUT -o lo -s <IP_ADDRESS>/32 -j RETURN ","time":"2021-06-01T11:14:11.315210878Z"}
2021-06-01T11:14:11.315206179Z | {"log":"-A OUTPUT -p tcp -j ISTIO_OUTPUT ","time":"2021-06-01T11:14:11.315206179Z"}
2021-06-01T11:14:11.315201579Z | {"log":"-A ISTIO_INBOUND -p tcp -j ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.315201579Z"}
2021-06-01T11:14:11.315196879Z | {"log":"-A ISTIO_INBOUND -p tcp --dport 15020 -j RETURN ","time":"2021-06-01T11:14:11.315196879Z"}
2021-06-01T11:14:11.315192279Z | {"log":"-A ISTIO_INBOUND -p tcp --dport 15021 -j RETURN ","time":"2021-06-01T11:14:11.315192279Z"}
2021-06-01T11:14:11.315187279Z | {"log":"-A ISTIO_INBOUND -p tcp --dport 15090 -j RETURN ","time":"2021-06-01T11:14:11.315187279Z"}
2021-06-01T11:14:11.315172179Z | {"log":"-A ISTIO_INBOUND -p tcp --dport 22 -j RETURN ","time":"2021-06-01T11:14:11.315172179Z"}
2021-06-01T11:14:11.315167579Z | {"log":"-A PREROUTING -p tcp -j ISTIO_INBOUND ","time":"2021-06-01T11:14:11.315167579Z"}
2021-06-01T11:14:11.315161079Z | {"log":"-A ISTIO_IN_REDIRECT -p tcp -j REDIRECT --to-ports 15006 ","time":"2021-06-01T11:14:11.315161079Z"}
2021-06-01T11:14:11.315156379Z | {"log":"-A ISTIO_REDIRECT -p tcp -j REDIRECT --to-ports 15001 ","time":"2021-06-01T11:14:11.315156379Z"}
2021-06-01T11:14:11.315151679Z | {"log":"-A ISTIO_INBOUND -p tcp --dport 15008 -j RETURN ","time":"2021-06-01T11:14:11.315151679Z"}
2021-06-01T11:14:11.315147279Z | {"log":"-N ISTIO_OUTPUT ","time":"2021-06-01T11:14:11.315147279Z"}
2021-06-01T11:14:11.315142579Z | {"log":"-N ISTIO_IN_REDIRECT ","time":"2021-06-01T11:14:11.315142579Z"}
2021-06-01T11:14:11.315138179Z | {"log":"-N ISTIO_REDIRECT ","time":"2021-06-01T11:14:11.315138179Z"}
2021-06-01T11:14:11.315133679Z | {"log":"-N ISTIO_INBOUND ","time":"2021-06-01T11:14:11.315133679Z"}
2021-06-01T11:14:11.315129079Z | {"log":"* nat ","time":"2021-06-01T11:14:11.315129079Z"}
2021-06-01T11:14:11.315122479Z | {"log":"Writing following contents to rules file: /tmp/iptables-rules-1622546051313506285.txt247778909 ","time":"2021-06-01T11:14:11.315122479Z"}
2021-06-01T11:14:11.315117979Z | {"log":" ","time":"2021-06-01T11:14:11.315117979Z"}
2021-06-01T11:14:11.315112779Z | {"log":"DNS_SERVERS=[],[] ","time":"2021-06-01T11:14:11.315112779Z"}
2021-06-01T11:14:11.315097879Z | {"log":"ENABLE_INBOUND_IPV6=false ","time":"2021-06-01T11:14:11.315097879Z"}
2021-06-01T11:14:11.314989279Z | {"log":"KUBEVIRT_INTERFACES= ","time":"2021-06-01T11:14:11.314989279Z"}
2021-06-01T11:14:11.314984679Z | {"log":"OUTBOUND_PORTS_EXCLUDE= ","time":"2021-06-01T11:14:11.314984679Z"}
2021-06-01T11:14:11.314979979Z | {"log":"OUTBOUND_PORTS_INCLUDE= ","time":"2021-06-01T11:14:11.314979979Z"}
2021-06-01T11:14:11.314975479Z | {"log":"OUTBOUND_IP_RANGES_EXCLUDE= ","time":"2021-06-01T11:14:11.314975479Z"}
2021-06-01T11:14:11.314971079Z | {"log":"OUTBOUND_IP_RANGES_INCLUDE=* ","time":"2021-06-01T11:14:11.314971079Z"}
2021-06-01T11:14:11.314966479Z | {"log":"INBOUND_PORTS_EXCLUDE=15090,15021,15020 ","time":"2021-06-01T11:14:11.314966479Z"}
2021-06-01T11:14:11.314961779Z | {"log":"INBOUND_PORTS_INCLUDE=* ","time":"2021-06-01T11:14:11.314961779Z"}
2021-06-01T11:14:11.314957079Z | {"log":"INBOUND_TPROXY_ROUTE_TABLE=133 ","time":"2021-06-01T11:14:11.314957079Z"}
2021-06-01T11:14:11.314952379Z | {"log":"INBOUND_TPROXY_MARK=1337 ","time":"2021-06-01T11:14:11.314952379Z"}
2021-06-01T11:14:11.314947779Z | {"log":"INBOUND_INTERCEPTION_MODE=REDIRECT ","time":"2021-06-01T11:14:11.314947779Z"}
2021-06-01T11:14:11.314943079Z | {"log":"PROXY_GID=1337 ","time":"2021-06-01T11:14:11.314943079Z"}
2021-06-01T11:14:11.31493848Z | {"log":"PROXY_UID=1337 ","time":"2021-06-01T11:14:11.31493848Z"}
2021-06-01T11:14:11.31493378Z | {"log":"PROXY_TUNNEL_PORT=15008 ","time":"2021-06-01T11:14:11.31493378Z"}
2021-06-01T11:14:11.31492928Z | {"log":"PROXY_INBOUND_CAPTURE_PORT=15006 ","time":"2021-06-01T11:14:11.31492928Z"}
2021-06-01T11:14:11.31492488Z | {"log":"PROXY_PORT=15001 ","time":"2021-06-01T11:14:11.31492488Z"}
2021-06-01T11:14:11.31492028Z | {"log":"---------- ","time":"2021-06-01T11:14:11.31492028Z"}
2021-06-01T11:14:11.31491578Z | {"log":"Variables: ","time":"2021-06-01T11:14:11.31491578Z"}
2021-06-01T11:14:11.31489488Z | {"log":" ","time":"2021-06-01T11:14:11.31489488Z"}
2021-06-01T11:14:11.31489008Z | {"log":"ISTIO_SERVICE_EXCLUDE_CIDR= ","time":"2021-06-01T11:14:11.31489008Z"}
2021-06-01T11:14:11.31488518Z | {"log":"ISTIO_SERVICE_CIDR= ","time":"2021-06-01T11:14:11.31488518Z"}
2021-06-01T11:14:11.31488048Z | {"log":"ISTIO_LOCAL_EXCLUDE_PORTS= ","time":"2021-06-01T11:14:11.31488048Z"}
2021-06-01T11:14:11.31487588Z | {"log":"ISTIO_OUTBOUND_PORTS= ","time":"2021-06-01T11:14:11.31487588Z"}
2021-06-01T11:14:11.31487098Z | {"log":"ISTIO_INBOUND_PORTS= ","time":"2021-06-01T11:14:11.31487098Z"}
2021-06-01T11:14:11.31486598Z | {"log":"ISTIO_INBOUND_TPROXY_ROUTE_TABLE= ","time":"2021-06-01T11:14:11.31486598Z"}
2021-06-01T11:14:11.31486088Z | {"log":"ISTIO_INBOUND_TPROXY_MARK= ","time":"2021-06-01T11:14:11.31486088Z"}
2021-06-01T11:14:11.31485598Z | {"log":"ISTIO_INBOUND_INTERCEPTION_MODE= ","time":"2021-06-01T11:14:11.31485598Z"}
2021-06-01T11:14:11.31485098Z | {"log":"INBOUND_CAPTURE_PORT= ","time":"2021-06-01T11:14:11.31485098Z"}
2021-06-01T11:14:11.31484598Z | {"log":"ENVOY_PORT= ","time":"2021-06-01T11:14:11.31484598Z"}
2021-06-01T11:14:11.31483858Z | {"log":"------------ ","time":"2021-06-01T11:14:11.31483858Z"}
2021-06-01T11:14:11.31479378Z | {"log":"Environment: ","time":"2021-06-01T11:14:11.31479378Z"}

I don't see any error messages in here. Can you search for "ERROR" or "WARN" in the log?

There is no more. Searched for "ERROR" and "WARN messages for the last 15 minutes, after I removed the pod again.
The Ui shows me now "Running", although the CLI kubectl shows CrashLoopBackOff.

PS C:\git\kyma-mtx-faq-management> kubectl get pods  --namespace project-faq
NAME                                   READY   STATUS             RESTARTS   AGE
faq-backend-746649fd4-sbjpr            1/2     CrashLoopBackOff   4          2m38s
faq-broker-5df55b575c-wbp9k            2/2     Running            2          23h
faq-exporter-5d4cbbf4f6-w4vf5          2/2     Running            0          23h
kyma-faq-ui-shell-6cc59bdcc5-pr9nn     2/2     Running            0          23h
project-faq-gateway-7557887b66-rvbk6   2/2     Running            0          23h

Tried to log it from cli, but struggle with a deprecated annotation.
kubectl logs -f -p faq-backend-746649fd4-sbjpr --namespace project-faq
Using deprecated annotation `kubectl.kubernetes.io/default-logs-container` in pod/faq-backend-746649fd4-sbjpr. Please use `kubectl.kubernetes.io/default-container` instead

There needs to be an error message somewhere (as the status is set to "CrashLoopBackOff"). It's hard to diagnoze this without the error message.

There needs to be an error message somewhere (as the status is set to "CrashLoopBackOff"). It's hard to diagnoze this without the error message.

this is why I tried to do it from command line.

I'm sorry this is causing you so much troubles on Windows. I asked a colleague (also a Windows user) to follow the instructions. Maybe he makes an insightful observation that can help.

No problem! I like it. Is a good reason to get deeper in K8s! :)

I just wiped my namespace and tested it and I can confirm that there is a problem.
And I found out what it was :)  : The creation of the "faq-saas-registry" didn't complete successfully.

As we're all running on the same trial landscape, we need to have unique app names. In short, you need to change two occurrences of faq-app  (have a look at the linked commit for details) to something unique (e.g. add your cluster id). This was causing the problem.
Thanks a lot for reporting this one!
I'll publish a fix right now, please confirm that this worked.
PS: You need to remove all deployments and service instances before running the kubectl apply commands again. You don't have the repeat the steps before thekubectl apply commands.

Sorry, but I can't confirm that.
faq-saas-registry was not in a pending status. It was running fine!

After checking the status for faq-saas-registry I removed the deployments and pods as you asked for.
Changed the appName: FaqManagement-c-2ac3840 and deployed all the .yaml files again.
I do have the same issue as before (faq-backend is not running).  faq-saas-registry is running fine.

I'm quite sure, that it has something to do with the wrong base64 secrets. (base64 //)
base64 (//57AA0ACgAgACIAYwBsAGkAZQBuAHQAaQBkAC...)
The pod shows me this error msg: caused: setenv: invalid argument: unknown
failed to start container "1705652c44339d596d74ef78ab79fe4c1e5e46fdf8a408162d3213535f6ab7fc": Error response from daemon: OCI runtime create failed: container_linux.go:370: starting container process caused: process_linux.go:459: container init caused: setenv: invalid argument: unknown
For this problem (caused: setenv: invalid argument: unknown) I found this:
https://github.com/opencontainers/runc/issues/1720
The reason seems to be a wrong base64 key.
If you don't have this issue, I think it must have something to do with the Windows kubectl CLI.

really strange...
My colleague (Windows user) was able to create the secret (and to see it) without any problems. He also noticed that tails is not available on Windows - so I added a not for this. So I don't this is a Windows problem - at least not one that affects all versions of Windows.
Can you try to create another opaque secret via kubectl and see this one in the console?

ok, I'm playing a little bit with the sm-credentials.
Could you tell me, if your sm-credentials yaml looks similar to mine?
And does your credentials starts with this "//" characters too?

Mine looks a little bit different. I doesn't start with // and it doesn't include the managedFields either.

would you let me know, what your kubectl version is?
PS C:\git\kyma-mtx-faq-management> kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.1", GitCommit:"5e58841cce77d4bc13713ad2b91fa0d961e69192", GitTreeState:"clean", BuildDate:"2021-05-12T14:18:45Z", GoVersion:"go1.16.4", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.17", GitCommit:"68b4e26caf6ede7af577db4af62fb405b4dd47e6", GitTreeState:"clean", BuildDate:"2021-03-18T00:54:02Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.21) and server (1.18) exceeds the supported minor version skew of +/-1

removed my newer client version and downgraded it to 1.18., but without success. same strange behavior (secrets) as before.
will close this ticket.
PS C:\git\kyma-mtx-faq-management> kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.0", GitCommit:"9e991415386e4cf155a24b1da15becaa390438d8", GitTreeState:"clean", BuildDate:"2020-03-25T14:58:59Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.17", GitCommit:"68b4e26caf6ede7af577db4af62fb405b4dd47e6", GitTreeState:"clean", BuildDate:"2021-03-18T00:54:02Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Tried it also from WSL, but the same result.

Can confirm that I have the exact same issue on a Win10Pro environment (tried it with different approaches too, including WSL2, without success).

ok, I'm playing a little bit with the sm-credentials.
I changed the credentials more times and removed all special characters, but the two "//" are always left in the base64 key.

I'll reopen the ticket as this definitely something that should be followed up upon.

The colleague who tested it on Windows is running
 kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T16:31:21Z", GoVersion:"go1.16.1", Compiler:"gc", Platform:"windows/amd64"}

And creates the following secret (without //):

To solve this issue I replaced the base64 with my own created base64 key. (https://www.base64encode.org/)
After that, the pods and deployments are running and I can see the "FAQ Saas Sample" in the new "Consumer"-Subaccount.

So, now I'm ready to continue the next steps...

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0"

I downgraded my CLI to GitVersion:"v1.21.0" but without any difference. Same strange behavior.

Tried to continue with the lesson and came to the next hurdle. There is still a problem with the faq-backend-746649fd4-z4sf4

But I think in this case is the reason the hdi-service.
Error: Conflict, description: instance with same name exists for the current tenant
2021-06-03T06:42:05.488018309Z | {"log":"npm ERR! errno 1 ","time":"2021-06-03T06:42:05.488018309Z"}
-- | --
2021-06-03T06:42:05.469842389Z | {"log":" at Object.error (/usr/src/app/node_modules/@sap/cds-mtx/node_modules/@sap/instance-manager/lib/polling-control.js:10:13) ","time":"2021-06-03T06:42:05.469842389Z"}
2021-06-03T06:42:05.469749489Z | {"log":"[HDI_CONTAINER_MANAGER] - Error: State of create operation is failed (resource type: /v1/service_instances, resource id: 9fe61cf3-a536-4cb2-8178-6319fc0e3547, operation id: f3ca6a92-accd-4caf-a991-db28c165de54), error: Conflict, description: instance with same name exists for the current tenant ","time":"2021-06-03T06:42:05.469749489Z"}

Any ideas?

Check if your Hana cloud instance is up and running and make sure the all IP address is allowed.

Finally I found the reason, why the k8s secret creation did not work well regarding the content of the secret.
In my case the cf service-key faq-saas-container faq-container-key > faq-container-key.json command created the file faq-container-key.json with UTF16 LE encoding (when executed in Powershell). Switching the encoding to UTF8 solves the original issue discussed here.

@pfefferf: You are right!
If you use Powershell you will get UTF16 LE, but if you use MINGW64 (bash) you will get UTF-8
This would explain, why some Win-User doesn't have this issue.
C/C++ for Visual Studio Code - MinGW
https://code.visualstudio.com/docs/cpp/config-mingw

Wow, that's a really nasty issue!
Thanks a lot for identifying this one. I'll update the readme.


feat: Publish/load pre-quantized models

Running quantized models significantly reduces the GPU memory required for inference. Instead of downloading the full model and quantizing it during the load, we can quantize the model offline and save it. At runtime the (smaller) quantized model can be loaded.
This PR includes 3 changes:

Updates to the bitsandbytes and transformers versions which support quantizing
A notebook for quantizing and publishing models
Logic to map known models to their pre-quantized versions.

Closes #4

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (3c7e0a0) 97.17% compared to head (2a98332) 96.13%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

src/autora/doc/runtime/predict_hf.py
72.72%
3 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #34      +/-   ##
==========================================
- Coverage   97.17%   96.13%   -1.05%
==========================================
  Files           3        3
  Lines         177      181       +4
==========================================
+ Hits          172      174       +2
- Misses          5        7       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Generate policies from standard resources to make creating policies easier

Easily create ACM policies for various sources of policy:
Some sample sources of policies might include:

k8s CRS e.g., roles, role bindings etc
REGO policies enforced by OPA
Kyverno policies
etc

The goal is to point to a source above and provide a placement detail, the this new tool can auto generate ACM policies.
A script may be the starting point, and then a CLI could be integrated to enhance this.

/assign gparvin

/kind feature

(To be presented at the Sept 30 community meeting)


Feature/92

Closes #92

Pull Request Test Coverage Report for Build 287

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 288:
0.0%

Covered Lines:
561

Relevant Lines:
561

💛  - Coveralls


Add error handling at MainScreenViewModel.

Issue

close #734

Overview (Required)

Add error handling at MainScreenViewModel.

Links

nothing

Screenshot

Before
After

App Crash

I didn't think it was so easy! Thanks!


MSID: 91033 Version: 2 DOI: 10.1101/2<IP_ADDRESS>3803

MSID: 91033
Version: 2
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>3803
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=91033
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>3803

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/91033v2
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>3803
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/91033/v2/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

@acollings Please could I check this assessment is OK with the two evidence terms?

@JGilbert-eLife edited, thanks!


Website not working 502 Bad Gateway

The website does not work as of now. I tested this on Firefox, Widows 10 and Android, Chrome. This is what I am given:

jazakAllah khairan - fixed. will add this to the uptime checker to watch it for the future in sha' Allah.


Accessibility

I there must bi sub section like Apps, Documents, Web at the search bar (Alt + Space)

Already tracked by https://github.com/microsoft/PowerToys/issues/8913


Addresses #1759 NTR valve endothelial cell

Addresses #1759 NTR valve endothelial cell
#gogoeditdiff
Appears to contain some extra changes from the recently merged PR #1727.

Declarations can happen depending on how you add new terms for import.  If you paste the IRIs straight into Protege, that => a declaration in the edit file.

Declarations can happen depending on how you add new terms for import. If you paste the IRIs straight into Protege, that => a declaration in the edit file.

Yes, I have done that for other tickets as it is listed as the first option here. The page says this method is "to be avoided" but does not give a reason and it has consistently worked for prior tickets.
The declarations appearing in this PR, however, are a surprise since I did not add them. If I had to guess, they may be coming from PR https://github.com/obophenotype/cell-ontology/pull/1727 since they all seem to appear there.
Regardless, I'll delete the declarations in this PR and then merge.

{ Off topic for this PR but: adding IRIs directly has the great advantage that it can be used instantly without having to wait for someone to help or disrupting your editing flow run a slow import update.  I wonder if we should tolerate it and have a clean-up job that removes stray declarations from the edtor's file. Alternatively maybe we could have some super minimal temp import update (say  IRI + label only) that editors can use rapidly while working on a PR, postponing a full update to later  - Maybe add to agenda for Monday tech call? }

The following new term has been added to CL and will be available in the next release:
CL:4030033 'valve endothelial cell'

Should this have the GO term attached to it like in https://github.com/obophenotype/cell-ontology/pull/1761?

Not totally sure about this... the reference notes they secrete paracrine molecules, but I have not found a reference that explicitly states VECs secrete extracellular matrix constituents. Activated VICs are noted explicitly to secrete fibrous matrix proteins (collagen), which is why the GO axiom was added to that term.
From https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4485434/:
"VECs also secrete paracrine factors, including nitric oxide, endothelin-1, and C-type natriuretic peptide. Most biochemical factors secreted by VECs (except endothelin-1) function to reduce the pathogenic phenotypes of VICs."
vs.
"In addition, VICs secrete fibrous matrix proteins, matrix metalloproteinases (such as MMP1 and MMP2), biochemical factors, and can differentiate into myofibroblasts or osteoblast-like cells or undergo cell death-mediated calcification"


Feature request: Trap ctrl-c during instance create and prompt ‘are you sure’

Instance create blocks on the queue to access a device and the provisioning process once a device is accessed. During this time, a user may mistakenly enter ctrl-c while attempting to copy text from the terminal session, or while intending to take an action in a different window. This aborts device provisioning, which is frustrating if unintended.
Suggest to add a trap that catches the ctrl-c input and prompts 'Are you sure you want to cancel device provisioning?'.
Consider leaving an alternative kill signal without a common keystroke to facilitate programmatically cancelling provisioning.

To be clear this does not abort the provisioning of the device on the
actual cluster. Instead it abort the client sitting in a poll loop waiting
for the device to become provisioned
On Tue, Aug 11, 2020 at 7:58 AM Jeffrey Urban<EMAIL_ADDRESS>wrote:

Instance create blocks on the queue to access a device and the
provisioning process once a device is accessed. During this time, a user
may mistakenly enter ctrl-c while attempting to copy text from the terminal
session, or while intending to take an action in a different window. This
aborts device provisioning, which is frustrating if unintended.
Suggest to add a trap that catches the ctrl-c input and prompts 'Are you
sure you want to cancel device provisioning?'.
Consider leaving an alternative kill signal without a common keystroke to
facilitate programmatically cancelling provisioning.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/f0cal/farm/issues/12, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABI6IL7C6KEM5Q23I37GHBLSAFE7HANCNFSM4P3CDIHA
.

Considering @AndreyShprengel comment above, needs some more thought on UX. Do we want people to be able to actually cancel (and return the device to availability ASAP)? Should cancellation use another mechanism? Are people at risk to abandon instances, tying up devices?


Notebook is generated failed with error "Value cannot be null".

System Information (please complete the following information):
Windows OS: Windows-11-Enterprise-21H2
ML.Net Model Builder 2022: <IP_ADDRESS>5801 (Main Build)
Microsoft Visual Studio Enterprise: 2022(17.3.0)
.Net: 6.0
Describe the bug

On which step of the process did you run into an issue:
Notebook is generated failed on the Consume page.

TestMatrix
https://testpass.blob.core.windows.net/test-pass-data/taxi-fare.csv
https://testpass.blob.core.windows.net/test-pass-data/recommendation-ratings.csv
To Reproduce
Steps to reproduce the behavior:

Select Create a new project from the Visual Studio start window.
Choose the C# Console App (.NET Core) project template.
Add model builder by right click on the project.
Select "Data classification" or "Value predication" or "Recommendation" or "Forecasting" scenario and data source to complete the training;
Click "Add to solution" button next to "Notebook" section on the Consume page.
On the "Add Notebook" dialog, give the Notebook name, then click "Add solution" button.

Expected behavior
The notebook should be generated successfully.
Screenshot

Additional context:
Repro on: Data classification, Value predication, Recommendation, Forecasting scenarios.

Removing Notebook https://github.com/dotnet/machinelearning-tools/pull/1555


Improve npm test: lint

Ugh... https://github.com/spalger/gulp-jshint/issues/88

Hmm, if we are fine with the tag-specific dependency here, I might as well add a sane JSCS reporter.


Question for PixTransform

Hello author(s), as mentioned in your paper, the guide image and the target image are directly mapped, Does this mean we can directly transform the guide image to the target image without the source image?

Hi, thank you for reaching out! The transformation is indeed from the guide to the target (high-res) , but to learn this transformation you still need a source image (low-res). What you don't need is the ground truth high resolution target image, which is why this method is unsupervised. Hope this makes it clearer!Riccardo -------- Original message --------From: shensheng<EMAIL_ADDRESS>Sun, 12 Apr 2020, 16:03To: riccardodelutio/PixTransform<EMAIL_ADDRESS>Subscribed<EMAIL_ADDRESS>[riccardodelutio/PixTransform] Question for PixTransform (#2)
Hello author(s), as mentioned in your paper, the guide image and the target image are directly mapped, Does this mean we can directly transform the guide image to the target image without the source image?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Regression in benchmarks...

Regressions occur in the following:

text_canvas_cached_layout.html.layout.average
text_canvas_color_grid.html.text_layout.average
text_dom_cached_layout.html.layout.average
text_dom_color_grid.html.text_layout.outlierRatio

See https://flutter-flutter-perf.skia.org/e/?begin=1610648124&end=1611361782&keys=X744151f3a1869facf837e9d3ae711558&requestType=0&xbaroffset=23230.
May be related to https://github.com/flutter/flutter/issues/74648; regressions occurred in the roll  #74126 for other benchmarks.

/cc @ferhatb

/cc @ferhatb

/cc @mdebbar

/cc @mdebbar

I think the regression happened in https://github.com/flutter/flutter/pull/74078, not https://github.com/flutter/flutter/pull/74126.

I think the regression happened in https://github.com/flutter/flutter/pull/74078, not https://github.com/flutter/flutter/pull/74126.

@yjbanov yes the regression happened in https://github.com/flutter/flutter/pull/74078.
This benchmark is measuring two things:

Duration of drawing the entire frame.
Duration of the text layout portion of the frame.

It does the above twice. Once with Dom measurement and once with Canvas measurement. Now both are replaced by a new implementation that supports rich text, so the benchmark numbers converged:

As seen in the screenshot, the new implementation is only slightly worse than the Canvas measurement, but still orders of magnitude better than Dom measurement.

When we look at the big picture, the entire frame duration numbers have converged too (Dom vs Canvas). The difference between the new numbers and the old Canvas numbers is negligible. See the pink and orange lines:

That said, I believe there are opportunities to improve the performance of the new text layout implementation. So I'll keep this issue open and reduce the priority.

@yjbanov yes the regression happened in https://github.com/flutter/flutter/pull/74078.
This benchmark is measuring two things:

Duration of drawing the entire frame.
Duration of the text layout portion of the frame.

It does the above twice. Once with Dom measurement and once with Canvas measurement. Now both are replaced by a new implementation that supports rich text, so the benchmark numbers converged:

As seen in the screenshot, the new implementation is only slightly worse than the Canvas measurement, but still orders of magnitude better than Dom measurement.

When we look at the big picture, the entire frame duration numbers have converged too (Dom vs Canvas). The difference between the new numbers and the old Canvas numbers is negligible. See the pink and orange lines:

That said, I believe there are opportunities to improve the performance of the new text layout implementation. So I'll keep this issue open and reduce the priority.


Alex Mayer / Sandy Mayer

Hi! First of all thank you for your amazing work! Your site is incredible!
I've been exploring the GOAT list these days and I think I've noticed what might be a mistake. There is a player called Alex Mayer ranked 484 but after having checked both Wikipedia and the official ATP site I think this Alex Mayer is in fact Sandy Mayer (ranked 121). When he won the Birmingham tournament (1973) he was not nicknamed Sandy yet, but simply Alex, as his full first name is Alexander. So I think you should fuse the two profiles.. and add one point to Sandy by the way :-)
Thanks again! Have a good day!

Fixed


Plot does not show

A very attractive pkg, with extreme simplicity. I wonder if you would be indulgent enough to look at the below and comment on why you think the plot is not working?
##############################
import numpy as np
from pdepy import parabolic
import matplotlib.pyplot as plt
%config InlineBackend.figure_formats = ['svg']
xn, xf, yn, yf = 40, 4.0, 40, 0.4
x = np.linspace(0, xf, xn + 1)
y = np.linspace(0, yf, yn + 1)
init = x ** 2 - 4 * x + 5
bound = 5 * np.exp(-y)
p, q, r, s = 1, 1, -3, 3
axis = x, y
conds = init, bound, bound
params = p, q, r, s
parabolic.solve(axis, params, conds, method="ec")
ax = plt.gca()
ax.axhline(y=0, color='#993399', linewidth=1)
ax.axvline(x=0, color='#993399', linewidth=1)
plt.rcParams['figure.figsize'] = [6, 6]
ax.plot(x, y, linewidth = 0.9)
ax.set_aspect(1)
ax.grid(True, linestyle='dotted', color='gray', linewidth=0.9)
plt.title( 'PDEPy Parabolic Explicit' )
plt.show()
#########################################
thanks
Gary

Oops, saw it as soon as I posted. I left out the line
###############
fig, axes = plt.subplots( 1 )
######################
Sorry about that.
Gary

see above comment


Sui client publish error

The SUI project has many source files and errors occur when publishing. What are the solutions to this problem?
Error executing transaction: Failure {
    error: "MovePackageTooBig { object_size: 109768, max_object_size: 102400 } in command 0",
}

The error is quite useful here and it basically tells the user that the package's size is too big.
You can read more about these limits here:
https://docs.sui.io/concepts/object-model#limits-on-transactions-objects-and-data
You might need to split your package into two smaller packages.

Is there any corresponding documentation or examples?
Thx.

Minimizing macro usage could be another thing to try as macro expansion can lead to large package sizes.
Regarding documentation, you mean documentation on how to split your packages or documentation on errors?

Yes, documentation on how to split packages.

That is mostly up to you as you understand best what your application is trying to achieve, and how you could logically split it up in different packages.

Thx. Is there any documentation or specifications for developing and using third-party move libraries?

After splitting out the 'base' project, the 'base' project was compiled successfully. But an error occurred when compiling the wowok project.
sui move build
> Failed to build Move modules: Failed to resolve dependencies for package 'wowok'

// wowok.toml
[package]
        name = "wowok"
        version = "0.1.2"
        #published-at = "0x98e5209cf5cf31a38ebde562681441d7544f38ee6a879266dc7273160635f6ba"

        [dependencies]
        Sui = { local = "../../../sui-mainnet-v1.34.2/crates/sui-framework/packages/sui-framework/"}
        Base = { override = true, local = "../../base/"}

        [addresses]
        wowok =  "0x0"
        sui =  "0x2"
        base = "0x3"

// base.toml
[package]
        name = "base"
        version = "0.0.1"
        #published-at = "0x98e5209cf5cf31a38ebde562681441d7544f38ee6a879266dc7273160635f6ba"

        [dependencies]
        Sui = { local = "../../../sui-mainnet-v1.34.2/crates/sui-framework/packages/sui-framework/"}

        [addresses]
        base =  "0x3"
        sui =  "0x2"


Installaion Fail - 'Error compiling objects for extension'

Hello,
I am trying to install ctcdecode in a docker environment with PyTorch 1.5.1 and Cuda 10.1 in it.
This is the Dockerfile:
FROM pytorch/pytorch:1.5.1-cuda10.1-cudnn7-devel

# install basics
RUN apt-get update -y
RUN apt-get install -y git curl ca-certificates bzip2 cmake tree htop bmon iotop sox libsox-dev libsox-fmt-all vim

# install ctcdecode
RUN git clone --recursive https://github.com/parlance/ctcdecode.git
RUN cd ctcdecode && pip install .

and this is the error I get:
ninja: build stopped: subcommand failed.
    Traceback (most recent call last):
      File "/opt/conda/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1423, in _run_ninja_build
        check=True)
      File "/opt/conda/lib/python3.7/subprocess.py", line 512, in run
        output=stdout, stderr=stderr)
    subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-req-build-zav02cia/setup.py", line 55, in <module>
        cmdclass={'build_ext': BuildExtension}
      File "/opt/conda/lib/python3.7/site-packages/setuptools/__init__.py", line 144, in setup
        return distutils.core.setup(**attrs)
      File "/opt/conda/lib/python3.7/distutils/core.py", line 148, in setup
        dist.run_commands()
      File "/opt/conda/lib/python3.7/distutils/dist.py", line 966, in run_commands
        self.run_command(cmd)
      File "/opt/conda/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/opt/conda/lib/python3.7/site-packages/setuptools/command/install.py", line 61, in run
        return orig.install.run(self)
      File "/opt/conda/lib/python3.7/distutils/command/install.py", line 545, in run
        self.run_command('build')
      File "/opt/conda/lib/python3.7/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/opt/conda/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/opt/conda/lib/python3.7/distutils/command/build.py", line 135, in run
        self.run_command(cmd_name)
      File "/opt/conda/lib/python3.7/distutils/cmd.py", line 313, in run_command
        self.distribution.run_command(command)
      File "/opt/conda/lib/python3.7/distutils/dist.py", line 985, in run_command
        cmd_obj.run()
      File "/opt/conda/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 87, in run
        _build_ext.run(self)
      File "/opt/conda/lib/python3.7/distutils/command/build_ext.py", line 340, in run
        self.build_extensions()
      File "/opt/conda/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 603, in build_extensions
        build_ext.build_extensions(self)
      File "/opt/conda/lib/python3.7/distutils/command/build_ext.py", line 449, in build_extensions
        self._build_extensions_serial()
      File "/opt/conda/lib/python3.7/distutils/command/build_ext.py", line 474, in _build_extensions_serial
        self.build_extension(ext)
      File "/opt/conda/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 208, in build_extension
        _build_ext.build_extension(self, ext)
      File "/opt/conda/lib/python3.7/distutils/command/build_ext.py", line 534, in build_extension
        depends=ext.depends)
      File "/opt/conda/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 437, in unix_wrap_ninja_compile
        with_cuda=with_cuda)
      File "/opt/conda/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1163, in _write_ninja_file_and_compile_objects
        error_prefix='Error compiling objects for extension')
      File "/opt/conda/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1436, in _run_ninja_build
        raise RuntimeError(message)
    RuntimeError: Error compiling objects for extension

Any ideas why the build fails?
Thank you,
Andrei

thanks for the report! will try to track down what's going on here...

Ties to https://github.com/SeanNaren/deepspeech.pytorch/issues/574

Hi, I used to have the similar problem but eventually find a solution that works for me, hopefully it is useful for others.
I used ubuntu in a virtual machine.
Then I installed these packages in conda virtual environment.

python 3.6 (conda create -n myproject python=3.6)
pytorch 1.0.0 (use conda command : conda install pytorch==1.0.0 torchvision==0.2.1 cuda100 -c pytorch)
sudo apt install build-essential , this install packages such as gcc, g++ and make

We can check whether g++ and gcc are installed properly using g++ --version and gcc --version command
With these, the compiling is working fine hopefully. Cheers!

Hey @Elizabeth65 is there any pip installation repo for build-essential?


getting: Polish WebP conversion can be only triggered when Polish setting is enabled

When I try to enable polish and webp in cloudflare_zone_settings_override resource I get:
Error: error from makeRequest: HTTP status 400: content "{"success":false,"errors":[{"code":1020,"message":"Polish WebP conversion can be only triggered when Polish setting is enabled"},{"code":1006,"message":"Unrecognized zone setting name"}],"messages":[],"result":null}"
According to documentation in https://www.terraform.io/docs/providers/cloudflare/r/zone_settings_override.html#webp:
webp. Note that the value specified will be ignored unless polish is turned on (i.e. is "lossless" or "lossy")
So I expect it to be ignored (or have polish enabled and then webp enabled) instead of getting the error.
$ terraform --version
Terraform v0.12.9

provider.aws v2.30.0
provider.cloudflare v2.0.0
provider.template v2.1.2

I'm getting the same error. It happens when creating a new cloudflare_zone_settings_override resource. Disabling webp, create resource with polish enabled, set webp to on again seems to work for me.

This happens for me in an existing cloudflare_zone_settings_override resource.
$terraform -version
Terraform v0.12.28
+ provider.aws v3.0.0
+ provider.cloudflare v2.9.0

@jakshi @maetthu @ZebraFlesh can one of you please provide a reproduction case for this one? I'm not sure I have enough to go off here.

@jakshi @maetthu @ZebraFlesh can one of you please provide a reproduction case for this one? I'm not sure I have enough to go off here.

Pretty straight forward, use a resource similar to the following:
resource "cloudflare_zone_settings_override" "test-resource" {
  zone_id = <your zone id>
  settings {
    polish           = "lossy"
    webp             = "on"  # webp needs to enabled after polish; it's a two step process that cannot be achieved in a single commit
  }
}

Pretty straight forward, use a resource similar to the following:
resource "cloudflare_zone_settings_override" "test-resource" {
  zone_id = <your zone id>
  settings {
    polish           = "lossy"
    webp             = "on"  # webp needs to enabled after polish; it's a two step process that cannot be achieved in a single commit
  }
}

Terraform v0.12.30

provider.cloudflare v2.6.0

Settings
    # speed
    polish           = "lossy"
    webp             = "on"

Output:

[2021-03-20T11:29:39.141Z] Error: HTTP status 400: Polish WebP conversion can be only triggered when Polish setting is enabled (1020)

[2021-03-20T11:29:39.141Z] Error: HTTP status 400: Polish WebP conversion can be only triggered when Polish setting is enabled (1020)

the polish setting was persisted, but the webp was not. On the second run both seem to apply fine.
[2021-03-20T11:44:31.609Z]           ~ webp                        = "off" -> "on"

i think the solution would be to make webp to have a block and put polish setting inside the webp block?

This is still an issue with. Same result as @KyleNesium described
Terraform v1.0.8
provider.cloudflare v3.1.0

i think the solution would be to make webp to have a block and put polish setting inside the webp block?

or the other way around
polish {
  mode = "lossy"
  webp = "on"
  avif = "on"
}

closing this as unresolved since there isn't anything we can do at the moment. the zone settings management will be overhauled in a future release and this is on the list to get some attention so we'll address it there (and not in the current resource).


Add time key to parameters

Check whether the Terrarium syntax for time dependent parameters would be a better representation. Otherwise, parameters are of the form:
{
  "name": "beta",
  "lb": 0.1,
  "ub": 0.2,
  "time": 22
  "label": "any"
}

@danbryce  I have some questions on this, since the examples I was thinking of earlier (from the July 2023 evaluation) have time-dependent parameters, but the time-dependence in the AMR appears to be folded in at the transition-level rather than the parameter-level.  I was wondering if you knew of any instances where the AMR expressed the time dependence within the parameter?
Example: This Petri net AMR has a piecewise-defined beta.  However, the fact that it is time-dependent is folded in not at the beta parameter (which is set to the constant value  0.048081000000000006) but rather in the transitions that include beta, ex: starting at line 1027 of the linked AMR:
    {      "target": "t1",      "expression": "I*S*ai*beta*Piecewise((1, (t >= 0) & (t < 82)), (0.4, (t >= 82) & (t < 198)), (0.55, (t >= 198) & (t < 282)), (0.6, (t >= 282) & (t < 327)), (0.55, (t >= 327) & (t < 370)), (0.3, (t >= 370) & (t < 429)), (0.4, (t >= 429) & (t < 468)), (0.15, (t >= 468) & (t < 527)), (0.2, (t >= 527) & (t < 548)), (0.3, (t >= 548) & (t < 562)), (0.35, (t >= 562) & (t < 609)), (0.4, (t >= 609) & (t < 670)), (0.5, (t >= 670) & (t < 731)), (0.4, (t >= 731) & (t < 1096)), (1, True))",      "expression_mathml": "<apply><times/><ci>I</ci><ci>S</ci><ci>ai</ci><ci>beta</ci><piecewise><piece><cn>1</cn><apply><and/><apply><geq/><ci>t</ci><cn>0</cn></apply><apply><lt/><ci>t</ci><cn>82</cn></apply></apply></piece><piece><cn>0.40000000000000002</cn><apply><and/><apply><geq/><ci>t</ci><cn>82</cn></apply><apply><lt/><ci>t</ci><cn>198</cn></apply></apply></piece><piece><cn>0.55000000000000004</cn><apply><and/><apply><geq/><ci>t</ci><cn>198</cn></apply><apply><lt/><ci>t</ci><cn>282</cn></apply></apply></piece><piece><cn>0.59999999999999998</cn><apply><and/><apply><geq/><ci>t</ci><cn>282</cn></apply><apply><lt/><ci>t</ci><cn>327</cn></apply></apply></piece><piece><cn>0.55000000000000004</cn><apply><and/><apply><geq/><ci>t</ci><cn>327</cn></apply><apply><lt/><ci>t</ci><cn>370</cn></apply></apply></piece><piece><cn>0.29999999999999999</cn><apply><and/><apply><geq/><ci>t</ci><cn>370</cn></apply><apply><lt/><ci>t</ci><cn>429</cn></apply></apply></piece><piece><cn>0.40000000000000002</cn><apply><and/><apply><geq/><ci>t</ci><cn>429</cn></apply><apply><lt/><ci>t</ci><cn>468</cn></apply></apply></piece><piece><cn>0.14999999999999999</cn><apply><and/><apply><geq/><ci>t</ci><cn>468</cn></apply><apply><lt/><ci>t</ci><cn>527</cn></apply></apply></piece><piece><cn>0.20000000000000001</cn><apply><and/><apply><geq/><ci>t</ci><cn>527</cn></apply><apply><lt/><ci>t</ci><cn>548</cn></apply></apply></piece><piece><cn>0.29999999999999999</cn><apply><and/><apply><geq/><ci>t</ci><cn>548</cn></apply><apply><lt/><ci>t</ci><cn>562</cn></apply></apply></piece><piece><cn>0.34999999999999998</cn><apply><and/><apply><geq/><ci>t</ci><cn>562</cn></apply><apply><lt/><ci>t</ci><cn>609</cn></apply></apply></piece><piece><cn>0.40000000000000002</cn><apply><and/><apply><geq/><ci>t</ci><cn>609</cn></apply><apply><lt/><ci>t</ci><cn>670</cn></apply></apply></piece><piece><cn>0.5</cn><apply><and/><apply><geq/><ci>t</ci><cn>670</cn></apply><apply><lt/><ci>t</ci><cn>731</cn></apply></apply></piece><piece><cn>0.40000000000000002</cn><apply><and/><apply><geq/><ci>t</ci><cn>731</cn></apply><apply><lt/><ci>t</ci><cn>1096</cn></apply></apply></piece><otherwise><cn>1</cn></otherwise></piecewise></apply>"     },

We have been handling parameters specified in the model as they appear natively, but allowing our request to override the model parameters.
If IIUC, the beta is still the parameter, but it’s multiplied by the Piecewise function.  I’d say that we already handle this (minus the support for the piecewise function). IMO the piecewise function is not related to the parameter, but rather the rate law.
If we wanted to express a piecewise beta, we’d need something of the form:
Model rate law: ISai*beta
Request parameters:
{
“name”: “beta”,
“lb”: 0.04808 * 1,
“ub” 0.04808 * 1,
“time”: [0, 82)
},
{
“name”: “beta”,
“lb”: 0.04808 * 0.4,
“ub” 0.04808 * 0.4,
“time”: [82, 198)
},
I’m not sure how much we care about doing this in the request if people are already happy with this other method.

On Sep 6, 2023, at 2:35 PM, dmosaphir @.***> wrote:
@danbryce I have some questions on this, since the examples I was thinking of earlier (from the July 2023 evaluation) have time-dependent parameters, but the time-dependence in the AMR appears to be folded in at the transition-level rather than the parameter-level. I was wondering if you knew of any instances where the AMR expressed the time dependence within the parameter?
Example: This Petri net AMR has a piecewise-defined beta. However, the fact that it is time-dependent is folded in not at the beta parameter (which is set to the constant value 0.048081000000000006) but rather in the transitions that include beta, ex: starting at line 1027 of the linked AMR:
{ "target": "t1", "expression": "ISaibetaPiecewise((1, (t >= 0) & (t < 82)), (0.4, (t >= 82) & (t < 198)), (0.55, (t >= 198) & (t < 282)), (0.6, (t >= 282) & (t < 327)), (0.55, (t >= 327) & (t < 370)), (0.3, (t >= 370) & (t < 429)), (0.4, (t >= 429) & (t < 468)), (0.15, (t >= 468) & (t < 527)), (0.2, (t >= 527) & (t < 548)), (0.3, (t >= 548) & (t < 562)), (0.35, (t >= 562) & (t < 609)), (0.4, (t >= 609) & (t < 670)), (0.5, (t >= 670) & (t < 731)), (0.4, (t >= 731) & (t < 1096)), (1, True))", "expression_mathml": "ISaibeta1t0t820.40000000000000002t82t1980.55000000000000004t198t2820.59999999999999998t282t3270.55000000000000004t327t3700.29999999999999999t370t4290.40000000000000002t429t4680.14999999999999999t468t5270.20000000000000001t527t5480.29999999999999999t548t5620.34999999999999998t562t6090.40000000000000002t609t6700.5t670t7310.40000000000000002t731t10961" },
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Time is not being stored in the parameters, but rather comes into the custom rate laws


Support for the K8s descheduler

Feature Request
There's a upstream Kubernetes tool called the descheduler available at https://github.com/kubernetes-sigs/descheduler. There are many application strategies for various workloads that it would be benefit if TCE could package, ship and support such a component.
Describe alternatives you've considered
N/A
Additional context
In Knative upstream there's a feature request to limit the lifetime of a pod. Doing this has two effects

Forces clients to be built in a resilient way
Improves the security posture as a compromised pod can only cause damage for only it's lifetime

The descheduler has a strategy to accomplish what we need via it's PodLifeTime eviction.

@dprotaso - TCE has limited badwidth, but can probably assist with the packaging.
cc @joshrosso

Including the descheduler as a package in TCE would definitely be interesting!
For now we don't have any timelines to include it, but we'd welcome contributions.


flutter: command not found

What

CI is failing on develop
Run flutter --version
/home/runner/work/_temp/b20832a8-798a-43b0-9b3d-80c54bd8e9b8.sh: line 1: flutter: command not found
Error: Process completed with exit code 127.

It's only the release workflows, Post submit is still passing.
The problem is the following:

We cache the flutter env
The cache is kept 7 days without use
The release workflows have a different cache key then the normal CI workflows

mmh…


Typewriter draws 5 cards even if no cards were returned

This was just fixed (when I fixed Surveillance)


psycopg.DataError: PostgreSQL text fields cannot contain NUL (0x00) bytes

Describe the bug
Running a simple embedding/indexing pipeline based on the pgvector integration (example).
Having no problem when running markdown files, when running the pipeline through pdf files, I get the following error on some pdfs:
psycopg.DataError: PostgreSQL text fields cannot contain NUL (0x00) bytes.
I wonder whether you all have come across this before and whether this might be a common case to solve for in document_writer.
I added a patch to that file to replace null bytes before attempting to write to pg vector
Error message
psycopg.DataError: PostgreSQL text fields cannot contain NUL (0x00) bytes.
Expected behavior
Would expect the pipeline to write valid content to the db, and perhaps ignore null bytes.
Additional context
The PDF includes images, tables, etc. This is the type of PDF I will likely be ingesting, as opposed to a super clean and simple one. The PDF is 28MB.
To Reproduce

Run the following (example) with a large PDF.

FAQ Check

[ ] Have you had a look at our new FAQ page?

System:

OS: macOS Monterey
GPU/CPU: Apple M1 Pro
Haystack version (commit or version number): 2.0.1
DocumentStore: pg-vector
Reader: none, only working on indexing pipeline
Retriever:none, only working on indexing pipeline

I'm moving this issue to the core-integrations repository because I think we should address this problem in the integration and not at the Haystack level, at least initially.

@alez007 Could you add more context, eg. code example or something.

Hi, sorry for the late reply, I moved on since then and used elasticsearch and that worked fine. I don't have access to that code anymore so can't really help out.
Thanks


Resign option in multiplayer

Hi,
Now that we have ability to add menu items, would it be possible to add an option the the menu in multiplayer for "Resign", currently its "end this game?" or "Quit", one requires everyone to agree, the other quits and doesnt show the stats page. However when you are playing 3+ teams, sometimes you want to quit, but still watch the rest of the game.
My thinking is that when you click "resign" your lord is insta-killed.

Killed by whom? You usually collect gold and ressources for a kill.  I think this option sounds good on paper but actually for many party games, people should just kill the lord. Thats not to difficult and you can also just send him out if you want to do that on purpose.
I think GG in the chat + end this game is a good option. In multiparty games, people should still kill the lord. There is nothing to preventing a 'dead' player from watching while his lord is still alive.

Fair point, I'm also thinking of the lobby software im wanting to set up and how it knows what a "win" is, but that's another issue entirely.
However, the game does seem to notice who us "responsible " for killing somebody, as if I suicide my lord (to watch a match) it sometimes gives the gold to a nearby lord who shot some of my units or villagers before I died.... not sure how accurate itd be though, maybe it is just who hurt you last...

You can get killed by lions, so I guess killed by no enemy player would be possible?

Yes, I have been a watcher of several games, so I deliberately die either by suicide or by lions placed on the map for that purpose, and what I have noticed is that if I die having never been attacked by another player, no one gets the reward, but if i am attacked in some way before i die, someone gets the reward. I have not looked into enough to know why it gives it to each player, but i suspect it is who last hurt me.


Secondary VNIC for IP/CN, compatible defaults for block volume/AD

Add experimental configuration for secondary VNICs
Use correct defaults by mode for block volume config
Use Kubernetes v1.25 by default

you need to run the oci-network-config

The host network can be set up other ways as well - this just exposes configuration for the created resources without being prescriptive.


Actions sometimes activated again all at once improperly

This has the result that all the dead units get up in order to die again. I would have said it's probably something to do with world streaming chunks improperly setting actionActivated to true, but now just looking at when it happened, it doesn't reproduce when scrubbing past the same point on the same run again, so maybe it is something to do with real-time playback instead?

This happens when spritesheets are rerendered after resizing everything to a smaller spritesheet: https://github.com/codecombat/codecombat/blob/master/app/lib/surface/LayerAdapter.coffee#L294 – maybe we need to maintain old animation frames when rerendering? At least rerender less often.

@sderickson how hard to maintain old animation frames when rerendering?

Maybe a few hours to figure out?

Fixed in c56ec2c, at least for SegmentedSprites!


Menu slide animation buggy

Bug report
Describe the bug
The right menu does not have a clean animation. It have a 2 times animations, which make it not smoothy.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Simply click on "New Column" to get it

Expected behavior
The animation should be in 1 time to make it smoother and good to see.
Screenshots

System information

OS: Linux Debian Deepin
Browser (if applies) Vivaldi (chromium based) and Chrome
Version of supabase-js: /
Version of Node.js: v14.16.1

Hey @Olyno 👋  - thanks for reporting this
We've just fixed this, and hopefully it'll be released today.

Dashboard app is deployed!


clippy: fix legacy_numeric_constants

Problem
some changes for bumping Rust version: https://github.com/anza-xyz/agave/pull/1309
https://rust-lang.github.io/rust-clippy/master/index.html#/legacy_numeric_constants
Summary of Changes
- std::NUMBER_TYPE::CONSTANT_NAME
+ NUMBER_TYPE::CONSTANT_NAME

Codecov Report
Attention: Patch coverage is 85.92593% with 19 lines in your changes are missing coverage. Please review.

Project coverage is 81.6%. Comparing base (186befe) to head (6f92ce6).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master    #1314     +/-   ##
=========================================
- Coverage    81.6%    81.6%   -0.1%
=========================================
  Files         867      867
  Lines      368767   368750     -17
=========================================
- Hits       300967   300928     -39
- Misses      67800    67822     +22


Error using show-example

#import "@preview/tidy:0.2.0": show-example

#show raw: show-example.show-example

```typ
Hello world
```

Produces the error
error: variables from outside the function are read-only and cannot be modified
   ┌─ @preview/tidy:0.2.0\src\show-example.typ:32:4
   │
32 │     mode = "markup"
   │     ^^^^

It's not really intended to be used like that. The bug is there for sure and easy to fix. However, show-example creates a new raw and that would result in a recursive show rule.

I can change that and prevent the creation of a new raw but show-example still wouldn't work quite as within docstrings because the scope is not passed down automatically and user-defined functions would not be available.

On the other hand, you could do which would work.
#let my-var = [34]
#show raw: show-example.show-example.with(scope: (my-var: my-var))

```typ
Hello world #my-var
```

Okay, I'll push some update that will allow doing that.


runtime: update SetFinalizer docs to cover cases of package level data

What version of Go are you using (go version)?
go1.7.1 linux/amd64
What did you see instead?
see this discussion for details: https://groups.google.com/forum/#!topic/golang-dev/JAgv8kBTgk4
summary:

in the latest implementation, there is not restrictions for the argument obj.
the docs should present that calling SetFinalizer for a package level data is meaningless.

/cc some of the runtime folks @aclements @RLH.

The existing docs is fine as is.
"The argument obj must be a pointer to an object allocated by
calling new, by taking the address of a composite literal, or by
taking the address of a local variable."
This means no other pointers are accepted, which includes
package level variables.

@minux, "This means no other pointers are accepted, which includes package level variables."
This is not the fact.

You confused the differences between documented behavior
and actual implemented behavior.
The documented behavior is almost always a strict subset of
actual implemented behavior, i.e. the code implements some
unspecified behavior. In general it's not wise to depend on
those unspecified behaviors.
For this particular case, the documentation says you can't use
package level variables, but the implementation doesn't enforce
this, so you can actually set finalizer on package level variables,
but as this is not documented to be valid, it's not guaranteed to
stay valid for future Go versions.
The current docs is the correct one, and there is no need to
complicate it further (esp. the current docs already enumerates
all valid cases, there is no need to explicitly say excluded cases
are invalid).

But if the document doesn't forbid package level pointers to objects allocated by calling new and by taking the address of composite literals, why it forbids general package level pointers?

If the document has no problems, can I file an issue for the compiler implementation?
After all, older compiler versions will create panic when argument obj is a pointer to package level data.
Whatever, the docs for SetFinalizer should be more detailed.

I tried some of the previous releases for setting finalizer on
package level variable. OK means no panic.
go version go1
runtime.SetFinalizer: pointer not at beginning of allocated block
go version go1.1.2 linux/amd64
runtime.SetFinalizer: pointer not at beginning of allocated block
go version go1.2.1 linux/amd64
runtime.SetFinalizer: pointer not at beginning of allocated block
go version go1.2.2 linux/amd64
runtime.SetFinalizer: pointer not at beginning of allocated block
go version go1.3 linux/amd64
OK
go version go1.3.3 linux/amd64
OK
go version go1.4 linux/amd64
OK
go version go1.4.1 linux/amd64
OK
go version go1.4.3 linux/amd64
OK
go version go1.5 linux/amd64
OK
go version go1.5.3 linux/amd64
OK
go version go1.6 linux/amd64
OK
go version go1.7.1 linux/amd64
OK
As you can see, this is not regression. The previous panic is actually
not because it's checking that the pointer is not on heap, it's because
it fails to find the beginning of allocated object on the heap. I don't
think we need to change the runtime to panic now as it used to panic
only by coincidence and the panic doesn't explain the real reason
anyway.

Good explanation, ok, I don't insist on change the docs any more.
But I think put a warning to using pointers to package level data in docs will be perfect.

There is a slight bug in the documentation. As written, it technically guarantees that SetFinalizer will panic if passed a pointer to a package-level variable. That clearly isn't the case. In fact, this claim is nonsense even if you ignore package-level variables, since we can't tell the difference between passing, say, a pointer to a composite literal and a pointer to its first element. So we should change this to say that it "may abort the program."
However, I'm inclined to change the guarantee here as well (and also the docs) to accept pointers to package-level variables just to simplify the API and its specification. I can't see how this would unduly constrain future implementations. @RLH?

@aclements @RLH Can we close this issue now?

@RLH and I chatted about whether to guarantee that SetFinalizer won't panic if passed a package-level variable. Neither of us have strong feelings about this either way, but the existing non-guarantee is more permissive for the implementation of finalizers and lets us change our minds later if there's more evidence. Further, it's important in general that SetFinalizer only be called for the beginning of an object, but we can't check that for package-level data, so we're leaning towards not trying to make any guarantees about pointers to package-level variables.
Hence, we're going to leave the documentation alone unless there's more compelling evidence for specifying this than the documentation being more restrictive than the implementation.

@aclements, @RLH,
the original title of this issue is "Make the SetFinalizer docs perfect".
I just feel the docs is some verbose.
For example, in the tip version, the docs says:

The argument obj must be a pointer to an object allocated by calling
new, by taking the address of a composite literal, or by taking the
address of a local variable.

So I think the following SetFinalizer callings for a, b, c will be always safe in later go versions:
package main

import (
	"runtime"
)

func callback1(*[]int) {}
func callback2(*int) {}

var a = &[]int{}
var b = new(int)

func main() {
	v := 123
	c := &v

	runtime.SetFinalizer(a, callback1)
	runtime.SetFinalizer(b, callback2)
	runtime.SetFinalizer(c, callback2)

	// ...

	// ....
}

However, the docs then says this:

It is not guaranteed that a finalizer will run for objects allocated
in initializers for package-level variables. Such objects may be
linker-allocated, not heap-allocated.

Now, I can't confirm if the SetFinalizer callings for a, b will be always safe or not.

@yaxinlx, maybe I don't understand what you mean by SetFinalizer being "safe". To me, SetFinalizer is "safe" in situations it guarantees won't panic. But your second quote from the documentation doesn't say anything about SetFinalizer panicking. It just says the finalizer may not run for a or b (which is true in general, since finalizers are never guaranteed to be run).

The complaint for the docs is I don't understand what the "must" mean in the first quote.
"must be xxx to possibly trigger a finalizer calling", "must be xxx to avoid paniking in later go versions"?
Thanks for your explanation. By your explanation, I think "must" means "must be xxx to avoid paniking in later go versions".

The complaint for the docs is I don't understand what the "must" mean in the first quote.
"must be xxx to possibly trigger a finalizer calling", "must be xxx to avoid paniking in later go versions"?

Either may be true. The point is that this is an intentionally underspecified contract between SetFinalizer and the caller of SetFinalizer. "The argument obj must be a pointer to an object allocated by calling new, by taking the address of a composite literal, or by taking the address of a local variable." means it's the caller's responsibility to pass an obj that satisfies these requirements. If the caller does something else, the behavior of SetFinalizer is unspecified. It may panic (a possibility suggested by the last sentence in that paragraph). It may do nothing (in which case the finalizer will never run). It may reboot your computer (though that would be rude). Who knows? And, as you point out, it may behave differently in other versions of Go or other implementations of Go (e.g., gccgo, GopherJS).


Resource prefix for lib project as the android gradle plugin

I am creating an aar, but I am afraid of resource conflict with the app, so would it possible to do a resource prefix like android gradle plugin?
In android gradle, when producing aar libs, we can add an option resourcePrefix 'prefix_' to add prefix to resources, so that it is hard to conflict with app resources.
Br,

Pretty low priority on this for me, if someone wants to point at how this
is implemented in gradle and possibly make a pull request, I would
appreciate it.
--
Sent from my phone
On Apr 30, 2015 8:04 PM, "Zaicheng Qi"<EMAIL_ADDRESS>wrote:

I am creating an aar, but I am afraid of resource conflict with the app,
so would it possible to do a resource prefix like android gradle plugin?
In android gradle, when producing aar libs, we can add an option resourcePrefix
'prefix_' to add prefix to resources, so that it is hard to conflict with
app resources.
Br,
—
Reply to this email directly or view it on GitHub
https://github.com/pfn/android-sdk-plugin/issues/166.

Thanks for the reply, I'll look into the gradle plugin and try to make it if possible.

I hate the Android SDK for its crippled xml namespacing. Prefixing is ugly but the only reasonable way around the SDK flaws. I didn't know that Gradle provided such a feature. Would love to see this here as well. It's obviously not super urgent, one can just hardcode the prefixes for now.
+1

So, I looked into this, it appears to be for creating new resources from Android Studio only. It does not translate existing names into this prefix. As such, I will likely not implement anything like this.

For reference https://android.googlesource.com/platform/tools/base/+/master/build-system/gradle/src/main/groovy/com/android/build/gradle/BaseExtension.groovy#130


Unable to use POST method

Hi,
Thank you for providing the great SDK.
I have tried to get weather data using a POST method like weather_api(URL, params=params, method="POST") according to this discussion.
But it raises the exception below.
requests.exceptions.HTTPError: 415 Client Error: Unsupported Media Type for url: https://archive-api.open-meteo.com/v1/archive...

My environments are as follows;
Python  3.11.6
requests 2.31.0
openmeteo_requests 1.2.0
requests-cache 1.2.1
retry-requests 2.0.0

Could you consider modifying the code like the one below to fix this problem?
--- openmeteo_requests/Client.py.orig
+++ openmeteo_requests/Client.py
@@ -24,7 +24,7 @@
     def _get(self, cls: type[T], url: str, params: any, method: str) -> list[T]:
         params["format"] = "flatbuffers"

-        response = self.session.request(method, url, params=params)
+        response = self.session.request(method, url, params=params, data=params)
         if response.status_code in [400, 429]:
             response_body = response.json()
             raise OpenMeteoRequestsError(response_body)

Regards,

Thanks for the report. I fixed it in https://github.com/open-meteo/python-requests/commit/103c53cd79cfa2000bbb3b409e3ff435c2421dcc and released in https://github.com/open-meteo/python-requests/releases/tag/v1.2.1

@patrick-zippenfenig Thanks for the updates. It works perfectly for me.


Run Codecov on PRs

Should work, feel free to test

@manniL thanks

@manniL review plz, not work

Now!


Redraw event won't trigger when using bucket only

When using the bucket/fill method only the redraw event won't be triggered.
When drawing with the normal free drawing mode and the using the bucket all works fine, when using the bucket on an empty canvas it won't.
Would be nice if that get's fixed.
Cheers.

Hello, I already suspect the cause of this bug so it should be an easy fix.
I also have a bigger update to release so I'll probably ship the fix with that, hopefully this weekend!
Thank you for the report, it's pretty sweet to know that someone else use this library!

I tried a couple of times to increase the performance of the fill function but it's still slower than what I'd like to.
If you'd like to pull a change or suggest anything to speed it up I'll be glad to merge or try it!
Staying in topic, this issue has been fixed on my local repository, I'll release it as soon as I finish add the new APIs to the docs.
Cheers.

Fixed in v1.3.0


Render image

HI, thank for great library.
I'm just have small problem, I not sure it is a bug or rich-textarea is not support this feature yet. I just want to display image instead of url when user uploaded image, but rich-textarea is not display image problaly, I'm tried use CSS to style but not have much effort
https://github.com/inokawa/rich-textarea/assets/123083837/0b4f83d6-08c3-4e4f-a319-8fbe72fac5f8
I use regex to parse image url
const renderer = createRegexRenderer([
  [
    HASHTAG_REG,
    ({ children, key }) => (

        {children}

    ),
  ],
  [
    URL_REG,
    ({ children, key, value }) => (

        {children}

    ),
  ],
  [
    IMAGE_REG,
    ({ children, key, value }) => (

    ),
  ],
]);

And rich textarea component
<RichTextarea
              value={text}
              onChange={(e) => setText(e.target.value)}
              placeholder={t("editor.placeholder")}
              className="resize-none border-none outline-none placeholder:text-neutral-600 focus:border-none focus:outline-none focus:ring-0 dark:placeholder:text-neutral-400"
              style={{ width: "100%", height: "100%" }}
              autoHeight
              autoFocus
>
  {renderer}
</RichTextarea>

Thank you for your interest in my lib. Unfortunately, it's impossible for now because rich-textarea is built on textarea element and it can render only texts.
It's possible to support image, video, etc in #74 if many people requested, but it's not scheduled yet.

https://github.com/inokawa/rich-textarea/issues/74#issuecomment-2459913554


Test all commits in CI

Currently, we merge branches as they are in the PR, without caring much about the individual commits. Note that this has not always been the case, I remember being asked to clean up individual commits in my first contributions to sbt.
In my experience, this not-so-nice history had made sbt difficult to debug using git bisect for several reasons:

Some commits do not compile
Some commits depend on -SNAPSHOTs
Some commits do not pass all the tests

One solution to solve this issue would be to use the squash and merge option from GitHub's UI when merging PRs that do not have a nice history. Unfortunately, Github doesn't create merge commits when using this option. Given that we want to keep the merge commits, we should probably go for having the CI test all commits.
Travis CI doesn't support testing all commits in a PR, so we need to either push each commit individually or move to another CI. A more complicated build script for Travis could also do the trick, but we would most likely hit the 60-minutes limit.

I think clean Git history is a worthy goal, but I am guessing this won't happen for a while, so I am closing this. PR or proposal around this would be welcome.


build: update validate-commits script to list valid types and scopes

The commit linter expects a certain type and/or scope in the commit message,
but if the right type/scope is not provided it doesn't tell us what to do.
Instead of this:
The following commit has an unknown type. You can use wip: to avoid this.

It now outputs this:
The following commit has an unknown type. It must be one of [docs, refactor, style, test, feat, fix, build, revert, ci, release]. You can use wip: to avoid this.

@kyliau with your change you actually print out the types and not the scopes. I do get confused sometimes with scope/type convention. 😜
I do agree with @dgp1130, that we should also print the valid scopes.

Revised the script to print out valid types and scopes.


Rule incorectly throws an error for valid attributes on SVG elements

This rule throws:
  Line 77:9:   Unknown property 'text-anchor' found, use 'textAnchor' instead  react/no-unknown-property
  Line 84:18:  Unknown property 'text-anchor' found, use 'textAnchor' instead  react/no-unknown-property

on this valid SVG code:
      <svg
        className="asset-class-details"
        top="25"
        height="48"
        width="72"
        ref={tooltip}
        text-anchor="middle" <===========
        style={{opacity: 0, ...legendStyle}}
      >
        <text height="48" width="72" style={{...legendStyle}} ref={tooltipName}>
          PLACEHOLDER
        </text>
        <div>
          <tspan text-anchor="middle" width="72" style={legendStyle} ref={tooltipAllocation}> <===========
            9.9%
          </tspan>
        </div>
      </svg>

And I don't want to disable the rule as it's useful in other contexts.

In react, the prop must be textAnchor, not text-anchor, regardless of what's appropriate for HTML. The same is true for most dash-case HTML attribute names.

You can see that React itself complains in the console about text-anchor being invalid, and suggests textAnchor, precisely as the lint rule correctly instructs you: https://jsfiddle.net/L5verkoq/