create-swap-delete VM Strategy resumes deployment from a wrong state if there was an error during VM creation

Describe the bug
CF Release Integration team has enabled the new experimental use-create-swap-delete-vm-strategy.yml ops file and we think we've found a bug.
Here is the timeline of what happened:

An upgrade of xenial stemcell from 98.28 to 170.2 triggered an upgrade deploy in our pipeline.
Deploy failed to create one of the VMs with the following error:Task 30998 | 00:14:49 | Compiling packages: percona-xtrabackup/a56dfd6f6551f39496503054b2589f2db2dcd405e1cbaab1dad7a8b458c37a1f (00:19:38)
Task 30998 | 00:15:28 | Creating missing vms: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1)
 < many other VMs created successfully; truncating output for brevity here>
Task 30998 | 00:29:05 | Creating missing vms: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:13:37)
                      L Error: Timed out pinging to 46079578-7258-41a9-a0b3-3daef54dcc14 after 600 seconds
Task 30998 | 00:29:05 | Error: Timed out pinging to 46079578-7258-41a9-a0b3-3daef54dcc14 after 600 seconds

We've decided it's an IaaS flake and re-run the deploy, which didn't detect it needs to download packages for all VMs it created, and instead downloaded packaged only for the doppler VM, which failed in the previous deploy. This resulted in a failed deployment:Task 31003 | 00:32:46 | Preparing deployment: Preparing deployment (00:00:27)
Task 31003 | 00:35:48 | Preparing package compilation: Finding packages to compile (00:00:01)
Task 31003 | 00:35:49 | Creating missing vms: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:01:18)
Task 31003 | 00:37:07 | Downloading packages: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:00:03)
Task 31003 | 00:37:10 | Updating instance adapter: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (canary)
Task 31003 | 00:37:10 | Updating instance nats: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0) (canary)
Task 31003 | 00:38:57 | Updating instance adapter: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (canary) (00:01:47)
Task 31003 | 00:38:57 | Updating instance adapter: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1) (00:01:19)
Task 31003 | 00:57:27 | Updating instance nats: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0) (canary) (00:20:17)
                     L Error: 'nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0)' is not running after update. Review logs for failed jobs: nats
Task 31003 | 00:57:27 | Error: 'nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0)' is not running after update. Review logs for failed jobs: nats

Failure was due nats job template referring to the IP of the old VM since the packages weren't updated.

To Reproduce
Follow steps in the timeline above, somehow imitating network failure to cause VM creation failure.
Expected behavior
Director should detect that it needs to download packages and render jobs on all new VMs.
Logs
Not sure which logs will be helpful here.
Versions (please complete the following information):

Infrastructure: AWS
BOSH version 268.0.1
BOSH CLI version 5.3.1-8366c6fd-2018-09-25T18:25:48Z
Stemcell version 97.28 -> 170.2

Deployment info:
cf-deployment with the ops file mentioned in bug description.

@ishustava I didn't see it in the issue description but maybe I missed it -- can you clarify if this failure occurred while turning create-swap-delete on for the first time or if the previous deployment (which succeeded) also had it turned on?

@jaresty both deployments had it enabled and, I believe, it was enabled before the first deployment started.

Any chance you share the contents of the rendered nats.conf with credentials redacted? I'm surprised to see any IP addresseses in that file since after applying the crate swap delete ops file the director should be filling in link addresseses as DNS names instead.

I don't think that feature will work if a job template intentionally gets the IP, which is the case for nats job. As a side note, the logic there is kind of complicated and probably today the line I linked can just be
net: <%= spec.ip %> as I have found out from #1476.
FWIW, cf upgrades with create-swap-delete work in the happy case scenario (if the above network error doesn't happen).

Hey @jaresty @mfine30, saw your conversation in Tracker and decided to reply here.
I might be missing something, but I think the fact that the nats job specifically asks for IP addresses might be a red herring.
We've done a few upgrades of CF successfully with create-swap-delete strategy turned on if VM creation doesn't fail due to network flakiness. I think this might be because both route_registrar and route_emitter consume nats addresses via instances[i].address from the nats link. NATs servers are not aware that they are in the cluster and, instead, NATs clients are cluster aware
What looks suspicious to me is the output of step 3, where only the packages for the doppler instance group were downloaded. In a happy case scenario, we're seeing that packages for all VMs are downloaded after VM creation completes successfully.

I'm not sure I'm understanding correctly-is this what you are seeing?

Deploy->upgrade deploy and fail->deploy which would succeed => rendered nats template has old ip address

Vs.

Deploy->upgrade deploy succeeds => rendered nats template has new ip address

Sorry for the confusion. We are seeing both.
In my previous comment I meant to say that we saw other upgrades (not including the one reported in this issue) succeed. In those cases, NATS job has the new IP in the template.
This bug described in my original post will fit scenario #1 you’ve mentioned. Scenario #2 describes other successful upgrades we have done with create swap delete turned on. I mentioned the successful cases to highlight the fact that we’ve seen successful upgrades with create-swap-delete turned on and NATS/NATS consumers being the way they are, so I think the issue is not NATS-specific, that seems like a red herring.

That is interesting.  Do you mind including the upgrade output from a successful upgrade for comparison?

Sure, here it is:
Using environment 'https://<IP_ADDRESS>:25555' as client 'admin'

Task 31121

Task 31121 | 19:11:52 | Preparing deployment: Preparing deployment (00:00:28)
Task 31121 | 19:14:34 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 31121 | 19:14:34 | Compiling packages: bitsgo/daf8d36bc46450c6ecdda2cdfecd616203453a91 (00:02:00)
Task 31121 | 19:17:09 | Creating missing vms: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0)
Task 31121 | 19:17:09 | Creating missing vms: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0)
Task 31121 | 19:17:09 | Creating missing vms: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1)
Task 31121 | 19:17:09 | Creating missing vms: database/8dcc0ce0-c6a6-4c38-b254-88485ada485b (0)
Task 31121 | 19:17:09 | Creating missing vms: database/ef31c418-d1a6-422e-ade0-8f841f043bbf (1)
Task 31121 | 19:17:09 | Creating missing vms: database/5282d1aa-719a-4afc-b387-7cbb52eccdac (2)
Task 31121 | 19:17:09 | Creating missing vms: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1)
Task 31121 | 19:17:09 | Creating missing vms: api/5f648cd8-28ca-4776-a136-453c8313e94e (1)
Task 31121 | 19:17:09 | Creating missing vms: diego-api/b9347e4f-0928-4e4c-a07a-9436d1cfa1ad (0)
Task 31121 | 19:17:09 | Creating missing vms: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0)
Task 31121 | 19:17:09 | Creating missing vms: log-api/825b6027-3c6e-4f4d-a6b2-5687d54224be (1)
Task 31121 | 19:17:09 | Creating missing vms: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0)
Task 31121 | 19:17:09 | Creating missing vms: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1)
Task 31121 | 19:17:09 | Creating missing vms: doppler/90a9c3a5-10f5-4e3e-a9d5-0b62577624d7 (2)
Task 31121 | 19:17:09 | Creating missing vms: diego-api/68882cea-be64-49e9-94fb-ec6b167d4974 (1)
Task 31121 | 19:17:09 | Creating missing vms: tcp-router/bef5c6ca-039e-4d5f-a616-3336f355ac46 (1)
Task 31121 | 19:17:09 | Creating missing vms: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3)
Task 31121 | 19:17:09 | Creating missing vms: scheduler/11ddf194-ae27-430c-be61-eb96d08156d1 (1)
Task 31121 | 19:17:09 | Creating missing vms: doppler/bcda4994-6d3a-4c5e-bb5f-12b9a68ee491 (1)
Task 31121 | 19:17:09 | Creating missing vms: tcp-router/0008d728-a7bb-4e97-b6bd-56c92e1fec07 (0)
Task 31121 | 19:17:09 | Creating missing vms: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0)
Task 31121 | 19:17:09 | Creating missing vms: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1)
Task 31121 | 19:17:09 | Creating missing vms: router/0199ce00-0c80-46f1-905d-6111896bbd08 (0)
Task 31121 | 19:17:09 | Creating missing vms: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0)
Task 31121 | 19:17:09 | Creating missing vms: scheduler/2117a22c-a670-40fd-be06-676255ae5c75 (0)
Task 31121 | 19:17:09 | Creating missing vms: router/6fd5053f-7045-4a84-b4dc-3e44b21d1354 (1)
Task 31121 | 19:17:09 | Creating missing vms: credhub/1552a7d5-bb4a-4d01-9d6f-6bcc16e88eb5 (0)
Task 31121 | 19:17:09 | Creating missing vms: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1)
Task 31121 | 19:17:09 | Creating missing vms: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0)
Task 31121 | 19:17:09 | Creating missing vms: doppler/0ba8ea77-a31a-4a08-8f1f-7fc463221147 (0)
Task 31121 | 19:17:09 | Creating missing vms: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1)
Task 31121 | 19:17:09 | Creating missing vms: log-api/2c085ced-2901-48ea-aed0-53d268b5dd57 (0)
Task 31121 | 19:19:11 | Creating missing vms: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0) (00:02:02)
Task 31121 | 19:19:12 | Creating missing vms: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1)
Task 31121 | 19:19:16 | Creating missing vms: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1) (00:02:07)
Task 31121 | 19:19:16 | Creating missing vms: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0)
Task 31121 | 19:20:02 | Creating missing vms: tcp-router/bef5c6ca-039e-4d5f-a616-3336f355ac46 (1) (00:02:53)
Task 31121 | 19:20:04 | Creating missing vms: tcp-router/0008d728-a7bb-4e97-b6bd-56c92e1fec07 (0) (00:02:55)
Task 31121 | 19:20:05 | Creating missing vms: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1) (00:02:56)
Task 31121 | 19:20:12 | Creating missing vms: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (00:03:03)
Task 31121 | 19:20:19 | Creating missing vms: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1) (00:03:10)
Task 31121 | 19:20:31 | Creating missing vms: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0) (00:03:22)
Task 31121 | 19:20:32 | Creating missing vms: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1) (00:03:23)
Task 31121 | 19:20:39 | Creating missing vms: router/6fd5053f-7045-4a84-b4dc-3e44b21d1354 (1) (00:03:30)
Task 31121 | 19:20:43 | Creating missing vms: log-api/825b6027-3c6e-4f4d-a6b2-5687d54224be (1) (00:03:34)
Task 31121 | 19:20:42 | Creating missing vms: router/0199ce00-0c80-46f1-905d-6111896bbd08 (0) (00:03:33)
Task 31121 | 19:20:52 | Creating missing vms: credhub/1552a7d5-bb4a-4d01-9d6f-6bcc16e88eb5 (0) (00:03:43)
Task 31121 | 19:21:02 | Creating missing vms: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0) (00:03:53)
Task 31121 | 19:21:14 | Creating missing vms: doppler/0ba8ea77-a31a-4a08-8f1f-7fc463221147 (0) (00:04:05)
Task 31121 | 19:21:19 | Creating missing vms: database/5282d1aa-719a-4afc-b387-7cbb52eccdac (2) (00:04:10)
Task 31121 | 19:21:19 | Creating missing vms: database/ef31c418-d1a6-422e-ade0-8f841f043bbf (1) (00:04:10)
Task 31121 | 19:21:23 | Creating missing vms: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0) (00:04:14)
Task 31121 | 19:21:24 | Creating missing vms: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0) (00:02:08)
Task 31121 | 19:21:27 | Creating missing vms: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1) (00:04:18)
Task 31121 | 19:21:27 | Creating missing vms: log-api/2c085ced-2901-48ea-aed0-53d268b5dd57 (0) (00:04:18)
Task 31121 | 19:21:27 | Creating missing vms: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1) (00:02:15)
Task 31121 | 19:21:28 | Creating missing vms: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0) (00:04:19)
Task 31121 | 19:21:32 | Creating missing vms: diego-api/b9347e4f-0928-4e4c-a07a-9436d1cfa1ad (0) (00:04:23)
Task 31121 | 19:21:32 | Creating missing vms: diego-api/68882cea-be64-49e9-94fb-ec6b167d4974 (1) (00:04:23)
Task 31121 | 19:21:36 | Creating missing vms: database/8dcc0ce0-c6a6-4c38-b254-88485ada485b (0) (00:04:27)
Task 31121 | 19:21:37 | Creating missing vms: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1) (00:04:28)
Task 31121 | 19:21:38 | Creating missing vms: doppler/90a9c3a5-10f5-4e3e-a9d5-0b62577624d7 (2) (00:04:29)
Task 31121 | 19:21:40 | Creating missing vms: doppler/bcda4994-6d3a-4c5e-bb5f-12b9a68ee491 (1) (00:04:31)
Task 31121 | 19:21:43 | Creating missing vms: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:04:34)
Task 31121 | 19:21:53 | Creating missing vms: api/5f648cd8-28ca-4776-a136-453c8313e94e (1) (00:04:44)
Task 31121 | 19:21:54 | Creating missing vms: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0) (00:04:45)
Task 31121 | 19:21:55 | Creating missing vms: scheduler/2117a22c-a670-40fd-be06-676255ae5c75 (0) (00:04:46)
Task 31121 | 19:21:56 | Creating missing vms: scheduler/11ddf194-ae27-430c-be61-eb96d08156d1 (1) (00:04:47)
Task 31121 | 19:21:56 | Downloading packages: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0)
Task 31121 | 19:21:56 | Downloading packages: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0)
Task 31121 | 19:21:56 | Downloading packages: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1)
Task 31121 | 19:21:56 | Downloading packages: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1)
Task 31121 | 19:21:56 | Downloading packages: database/ef31c418-d1a6-422e-ade0-8f841f043bbf (1)
Task 31121 | 19:21:56 | Downloading packages: database/5282d1aa-719a-4afc-b387-7cbb52eccdac (2)
Task 31121 | 19:21:56 | Downloading packages: diego-api/b9347e4f-0928-4e4c-a07a-9436d1cfa1ad (0)
Task 31121 | 19:21:56 | Downloading packages: diego-api/68882cea-be64-49e9-94fb-ec6b167d4974 (1)
Task 31121 | 19:21:56 | Downloading packages: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0)
Task 31121 | 19:21:56 | Downloading packages: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0)
Task 31121 | 19:21:56 | Downloading packages: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0)
Task 31121 | 19:21:56 | Downloading packages: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1)
Task 31121 | 19:21:56 | Downloading packages: router/0199ce00-0c80-46f1-905d-6111896bbd08 (0)
Task 31121 | 19:21:56 | Downloading packages: database/8dcc0ce0-c6a6-4c38-b254-88485ada485b (0)
Task 31121 | 19:21:56 | Downloading packages: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0)
Task 31121 | 19:21:56 | Downloading packages: scheduler/11ddf194-ae27-430c-be61-eb96d08156d1 (1)
Task 31121 | 19:21:56 | Downloading packages: api/5f648cd8-28ca-4776-a136-453c8313e94e (1)
Task 31121 | 19:21:56 | Downloading packages: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1)
Task 31121 | 19:21:56 | Downloading packages: tcp-router/bef5c6ca-039e-4d5f-a616-3336f355ac46 (1)
Task 31121 | 19:21:56 | Downloading packages: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1)
Task 31121 | 19:21:56 | Downloading packages: doppler/90a9c3a5-10f5-4e3e-a9d5-0b62577624d7 (2)
Task 31121 | 19:21:56 | Downloading packages: scheduler/2117a22c-a670-40fd-be06-676255ae5c75 (0)
Task 31121 | 19:21:56 | Downloading packages: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3)
Task 31121 | 19:21:56 | Downloading packages: credhub/1552a7d5-bb4a-4d01-9d6f-6bcc16e88eb5 (0)
Task 31121 | 19:21:56 | Downloading packages: doppler/0ba8ea77-a31a-4a08-8f1f-7fc463221147 (0)
Task 31121 | 19:21:56 | Downloading packages: router/6fd5053f-7045-4a84-b4dc-3e44b21d1354 (1)
Task 31121 | 19:21:56 | Downloading packages: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0)
Task 31121 | 19:21:56 | Downloading packages: tcp-router/0008d728-a7bb-4e97-b6bd-56c92e1fec07 (0)
Task 31121 | 19:21:56 | Downloading packages: doppler/bcda4994-6d3a-4c5e-bb5f-12b9a68ee491 (1)
Task 31121 | 19:21:56 | Downloading packages: log-api/2c085ced-2901-48ea-aed0-53d268b5dd57 (0)
Task 31121 | 19:21:56 | Downloading packages: log-api/825b6027-3c6e-4f4d-a6b2-5687d54224be (1)
Task 31121 | 19:21:56 | Downloading packages: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1)
Task 31121 | 19:22:30 | Downloading packages: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1) (00:00:34)
Task 31121 | 19:22:30 | Downloading packages: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1) (00:00:34)
Task 31121 | 19:22:30 | Downloading packages: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1)
Task 31121 | 19:22:30 | Downloading packages: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0)
Task 31121 | 19:22:31 | Downloading packages: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0) (00:00:35)
Task 31121 | 19:22:31 | Downloading packages: router/0199ce00-0c80-46f1-905d-6111896bbd08 (0) (00:00:35)
Task 31121 | 19:22:33 | Downloading packages: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1) (00:00:37)
Task 31121 | 19:22:33 | Downloading packages: tcp-router/bef5c6ca-039e-4d5f-a616-3336f355ac46 (1) (00:00:37)
Task 31121 | 19:22:34 | Downloading packages: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (00:00:38)
Task 31121 | 19:22:36 | Downloading packages: doppler/90a9c3a5-10f5-4e3e-a9d5-0b62577624d7 (2) (00:00:40)
Task 31121 | 19:22:37 | Downloading packages: diego-api/b9347e4f-0928-4e4c-a07a-9436d1cfa1ad (0) (00:00:41)
Task 31121 | 19:22:37 | Downloading packages: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:00:41)
Task 31121 | 19:22:38 | Downloading packages: log-api/2c085ced-2901-48ea-aed0-53d268b5dd57 (0) (00:00:42)
Task 31121 | 19:22:39 | Downloading packages: tcp-router/0008d728-a7bb-4e97-b6bd-56c92e1fec07 (0) (00:00:43)
Task 31121 | 19:22:40 | Downloading packages: log-api/825b6027-3c6e-4f4d-a6b2-5687d54224be (1) (00:00:44)
Task 31121 | 19:22:42 | Downloading packages: router/6fd5053f-7045-4a84-b4dc-3e44b21d1354 (1) (00:00:46)
Task 31121 | 19:22:43 | Downloading packages: doppler/bcda4994-6d3a-4c5e-bb5f-12b9a68ee491 (1) (00:00:47)
Task 31121 | 19:22:46 | Downloading packages: diego-api/68882cea-be64-49e9-94fb-ec6b167d4974 (1) (00:00:50)
Task 31121 | 19:22:48 | Downloading packages: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0) (00:00:52)
Task 31121 | 19:22:49 | Downloading packages: doppler/0ba8ea77-a31a-4a08-8f1f-7fc463221147 (0) (00:00:53)
Task 31121 | 19:22:54 | Downloading packages: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0) (00:00:24)
Task 31121 | 19:23:06 | Downloading packages: credhub/1552a7d5-bb4a-4d01-9d6f-6bcc16e88eb5 (0) (00:01:10)
Task 31121 | 19:23:16 | Downloading packages: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1) (00:00:46)
Task 31121 | 19:23:36 | Downloading packages: api/5f648cd8-28ca-4776-a136-453c8313e94e (1) (00:01:40)
Task 31121 | 19:23:41 | Downloading packages: scheduler/2117a22c-a670-40fd-be06-676255ae5c75 (0) (00:01:45)
Task 31121 | 19:23:41 | Downloading packages: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1) (00:01:45)
Task 31121 | 19:23:42 | Downloading packages: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0) (00:01:46)
Task 31121 | 19:23:44 | Downloading packages: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0) (00:01:48)
Task 31121 | 19:23:46 | Downloading packages: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1) (00:01:50)
Task 31121 | 19:23:46 | Downloading packages: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0) (00:01:50)
Task 31121 | 19:23:48 | Downloading packages: database/ef31c418-d1a6-422e-ade0-8f841f043bbf (1) (00:01:52)
Task 31121 | 19:23:49 | Downloading packages: database/8dcc0ce0-c6a6-4c38-b254-88485ada485b (0) (00:01:53)
Task 31121 | 19:23:49 | Downloading packages: scheduler/11ddf194-ae27-430c-be61-eb96d08156d1 (1) (00:01:53)
Task 31121 | 19:23:52 | Downloading packages: database/5282d1aa-719a-4afc-b387-7cbb52eccdac (2) (00:01:56)
Task 31121 | 19:23:56 | Downloading packages: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1) (00:02:00)
Task 31121 | 19:24:01 | Downloading packages: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0) (00:02:05)
Task 31121 | 19:24:01 | Updating instance adapter: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (canary)
Task 31121 | 19:24:01 | Updating instance nats: nats/2a3323f3-6889-49ad-8e2f-ce5b1b794525 (0) (canary) (00:00:44)
Task 31121 | 19:24:45 | Updating instance nats: nats/060195cb-5efd-4896-bce4-bc749f01cceb (1) (00:00:18)
Task 31121 | 19:25:43 | Updating instance adapter: adapter/318f900f-7462-4d90-a997-c373f9c57b68 (0) (canary) (00:01:42)
Task 31121 | 19:25:43 | Updating instance adapter: adapter/94f6f903-225b-45e1-85f4-dd87b1c1a559 (1) (00:01:16)
Task 31121 | 19:26:59 | Updating instance database: database/8dcc0ce0-c6a6-4c38-b254-88485ada485b (0) (canary) (00:01:43)
Task 31121 | 19:28:42 | Updating instance database: database/ef31c418-d1a6-422e-ade0-8f841f043bbf (1) (00:01:33)
Task 31121 | 19:30:15 | Updating instance database: database/5282d1aa-719a-4afc-b387-7cbb52eccdac (2) (00:01:32)
Task 31121 | 19:31:47 | Updating instance diego-api: diego-api/b9347e4f-0928-4e4c-a07a-9436d1cfa1ad (0) (canary) (00:00:45)
Task 31121 | 19:32:32 | Updating instance diego-api: diego-api/68882cea-be64-49e9-94fb-ec6b167d4974 (1) (00:00:36)
Task 31121 | 19:33:08 | Updating instance api: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0) (canary)
Task 31121 | 19:33:08 | Updating instance bits: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0) (canary)
Task 31121 | 19:33:08 | Updating instance cc-worker: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0) (canary)
Task 31121 | 19:33:08 | Updating instance uaa: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0) (canary)
Task 31121 | 19:33:54 | Updating instance bits: bits/1216c5ff-3346-44da-9670-601c83ccde4a (0) (canary) (00:00:46)
Task 31121 | 19:33:54 | Updating instance bits: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1)
Task 31121 | 19:33:54 | Updating instance cc-worker: cc-worker/481cbbe9-70f5-4de8-b6f8-cce8b683b172 (0) (canary) (00:00:46)
Task 31121 | 19:33:54 | Updating instance cc-worker: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1)
Task 31121 | 19:34:14 | Updating instance bits: bits/a838c388-ee19-4a6d-9eb4-d48a49848cc2 (1) (00:00:20)
Task 31121 | 19:34:16 | Updating instance cc-worker: cc-worker/c106bad4-d35b-4a56-9c2b-e73d12e17933 (1) (00:00:22)
Task 31121 | 19:34:43 | Updating instance api: api/b62f8597-b0ed-4978-8bd3-f7e7bf44b8d1 (0) (canary) (00:01:35)
Task 31121 | 19:34:43 | Updating instance api: api/5f648cd8-28ca-4776-a136-453c8313e94e (1)
Task 31121 | 19:35:11 | Updating instance uaa: uaa/ee43f3a5-1a34-46ca-a58f-7aec6174db7a (0) (canary) (00:02:03)
Task 31121 | 19:35:11 | Updating instance uaa: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1)
Task 31121 | 19:36:11 | Updating instance api: api/5f648cd8-28ca-4776-a136-453c8313e94e (1) (00:01:28)
Task 31121 | 19:37:19 | Updating instance uaa: uaa/0f607b25-08cf-4798-8682-25a58c552db9 (1) (00:02:08)
Task 31121 | 19:37:19 | Updating instance router: router/0199ce00-0c80-46f1-905d-6111896bbd08 (0) (canary) (00:02:51)
Task 31121 | 19:40:10 | Updating instance router: router/6fd5053f-7045-4a84-b4dc-3e44b21d1354 (1) (00:02:55)
Task 31121 | 19:43:05 | Updating instance tcp-router: tcp-router/0008d728-a7bb-4e97-b6bd-56c92e1fec07 (0) (canary) (00:00:58)
Task 31121 | 19:44:03 | Updating instance tcp-router: tcp-router/bef5c6ca-039e-4d5f-a616-3336f355ac46 (1) (00:01:03)
Task 31121 | 19:45:06 | Updating instance scheduler: scheduler/2117a22c-a670-40fd-be06-676255ae5c75 (0) (canary) (00:00:48)
Task 31121 | 19:45:54 | Updating instance scheduler: scheduler/11ddf194-ae27-430c-be61-eb96d08156d1 (1) (00:00:55)
Task 31121 | 19:46:49 | Updating instance diego-cell: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0) (canary)
Task 31121 | 19:46:49 | Updating instance doppler: doppler/0ba8ea77-a31a-4a08-8f1f-7fc463221147 (0) (canary) (00:00:51)
Task 31121 | 19:47:40 | Updating instance doppler: doppler/90a9c3a5-10f5-4e3e-a9d5-0b62577624d7 (2) (00:00:40)
Task 31121 | 19:48:20 | Updating instance doppler: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3)
Task 31121 | 19:48:26 | Updating instance diego-cell: diego-cell/3128a3bf-0b26-4c8f-aa95-bd21f92f2e35 (0) (canary) (00:01:37)
Task 31121 | 19:48:26 | Updating instance diego-cell: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1)
Task 31121 | 19:49:00 | Updating instance doppler: doppler/8b3d6e73-02d0-4b17-9a48-e918b7c199f5 (3) (00:00:40)
Task 31121 | 19:49:00 | Updating instance doppler: doppler/bcda4994-6d3a-4c5e-bb5f-12b9a68ee491 (1) (00:00:40)
Task 31121 | 19:50:03 | Updating instance diego-cell: diego-cell/2f378dd6-fcbf-4c52-bf44-209573e13bfa (1) (00:01:37)
Task 31121 | 19:50:03 | Updating instance log-api: log-api/2c085ced-2901-48ea-aed0-53d268b5dd57 (0) (canary) (00:01:43)
Task 31121 | 19:51:46 | Updating instance log-api: log-api/825b6027-3c6e-4f4d-a6b2-5687d54224be (1) (00:01:18)
Task 31121 | 19:53:04 | Updating instance nozzle: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0) (canary)
Task 31121 | 19:53:04 | Updating instance credhub: credhub/1552a7d5-bb4a-4d01-9d6f-6bcc16e88eb5 (0) (canary) (00:01:05)
Task 31121 | 19:54:09 | Updating instance credhub: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1)
Task 31121 | 19:54:24 | Updating instance nozzle: nozzle/a31b05e8-926e-4fe8-93f1-e6e2f09f0bfb (0) (canary) (00:01:20)
Task 31121 | 19:55:14 | Updating instance credhub: credhub/2501cfdb-564b-4e63-8916-fef4c9c218f3 (1) (00:01:05)

Task 31121 Started  Wed Oct 31 19:11:52 UTC 2018
Task 31121 Finished Wed Oct 31 19:55:14 UTC 2018
Task 31121 Duration 00:43:22
Task 31121 done

Succeeded

I've also seen similar networking issues with create-swap-delete, you can find my deployment logs here: https://gist.github.com/9ad197b11dff26116d9b292b6cba0c36.

Hey @ishustava,
We are having a tough time reproducing this. In our reproduction, we see that the Downloading packages line only shows up for the newly created VM, but every previously created VM that gets reused still gets updated packages / templates.
Is there any chance you could provide us with the debug log for the task that resulted in the deploy failure (31003) and task which failed to create the VM (30998)? Have you seen this multiple times, or was this the only instance?
Best,
@jfmyers9 && @dpb587-pivotal, CF BOSH

Hey @jfmyers9 & @dpb587-pivotal,
Thanks for looking into it. We have only seen this issue once and have since disabled it in our pipelines for other reasons.
I've attached the two debug logs:
30998_debug.log
31003_debug.log

//cc @thomas1206 @bingosummer

We think this commit (https://github.com/cloudfoundry/bosh/commit/9142f3583dd6fd7b8c2dd3744e715bf10686cebd) could fix the issue. But since we could never successfully reproduce the bug, we can't be sure. Could you try it out and let us know if you still see the error?
Best,
@pivotal-mp && @jrussett, CF BOSH


Error 500

How to repeat this if:
Open https://nebula.hersel.it/blacklist?tgid=SOMELETTERS
Result:
Internal Server Error
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Summary:
When you enter letters in tgid parameter server returns error without handling it with API

@simobit Thanks for reporting, I'll fix this bug


Creates the argument min-cpu-platform for the google-v2 provider

Creates the argument min-cpu-platform for the google-v2 provider. This permits the specification of a CPU Platform such as, e.g., "Intel Skylake", which is required for certain instruction sets such as AVX2, and for certain machine types (such as any machine that has more than 64 cores). This also resolves Issue #117

Thank-you @carbocation for the contribution!
It turns out we have a release we are pushing out this week, which includes the addition of --cpu-platform for the v2 provider, which looks a lot like your PR. Will update here when the release is published.

(This is solved separately by 82bc6b0 so I'm closing this pull request.)


Upgrade s3 client

bump to aws-sdk to v2 which defaults to signature_version v4 since v2.2 and update the codepaths for the new api / deprecated methods.
I manually ran the upload code in a repl to test it works instead of relying on a double to receive messages.
https://github.com/aws/aws-sdk-ruby/blob/master/UPGRADING.md#aws-sdk-core---v220
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

No it uses the storage adapter to do the interaction with s3. I've got a new PR (that needs a rebase) to update it to fix the upload path and add an encryption check.


Slip simulation

"Hello,
I'm currently using the Mujoco simulator to create a dataset by attaching a sensor to the end of a gripper. I'm trying to simulate a scenario where the gripper grasps an object and moves it, applying an external force to make the object slide. However, even after grasping, the object slips regardless of the grasping force applied by the gripper. I would appreciate any advice on how to address this issue.
Thank you."

https://mujoco.readthedocs.io/en/latest/modeling.html#preventing-slip


Delay - mainly after doesn't work using persistent state.

Description
Hi,
I'm using Xstate machine npm module in server side.
I have states configured as bellow
{
"id" : "serviceMachine",
"initial" : "ACTIVE",
"context" : {
"noTopUp" : "2021-02-18 10:34",
"noUsage" : "2021-02-16 22:25"
},
"states" : {
"ACTIVE" : {
"after" : {
"NoTopUpToFree" : "checkTopup"
},
"on" : {
"SUSPEND" : "SUSPEND",
"SYNC" : "ACTIVE",
"TERMINATE" : "TERMINATE"
}
},
"checkTopup" : {
"invoke" : {
"src" : "checkTopUpDB",
"onDone" : "ACTIVE",
"onError" : {
"target" : "SUSPEND"
}
}
},
"SUSPEND" : {
"after" : {
"ActiveDelay" : "ACTIVE"
},
"on" : {
"TERMINATE" : "TERMINATE",
"RESUME" : "ACTIVE"
}
},
"TERMINATE" : {}
}
}
all the delays are simple delays which return 10 ms or 12 ms. when we save data on each transition.delays work perfectly when server is up and start was started from init state.
but when i reslove the persistent state, I don't see actions of any delays. for resolving state i'm using resolveState(State.create())
Expected Result
Should trigger delay events .
Actual Result
No actions in state object.
Reproduction
Use the Machine  configuration as above, save each transition.  before NoTopUpToFree ends trigger SUSPEND event.once its suspended. close the server.
Restart it again, it should trigger RESUME on ActiveDelay done.(expected but not working)
Please let me know if its a bug or its not the right way @davidkpiano
Regards,
Vinod Kumar Pula

Please always try to share a repro case in a runnable form - either by providing a git repository to clone or a codesandbox. OSS maintainers usually can't afford the time to set up the repro, even if exact steps are given.
And also while sharing the code please make sure that it's formatted well so people can actually read it.

Based on the code you currently have, I assume you're missing the delays in the second argument: createMachine(definition, { delays: { ... } }).
I will reopen this if there is a full repro. Please create a CodeSandbox (XState template) reproduction of this. Thanks!


ShellItem Properties - System.Runtime.InteropServices.COMException

Describe the bug
Sorry, I'm bugging you again. The following code results in a System.Runtime.InteropServices.COMException.
What code is involved
var si = new ShellItem(@"C:\ANY_FILE_PATH");
var key = si.PropertyDescriptions.First().PropertyKey; ---> ok
var prop1 = si.Properties[key]; ---> exception
var prop2 = si.Properties.Keys; ----> exception
var prop3 = si.Properties.First(); ----> exception

Stack trace

in Vanara.PInvoke.Shell32.IShellItem2.GetPropertyStore(GETPROPERTYSTOREFLAGS flags, Guid& riid)
in Vanara.Windows.Shell.ShellItemPropertyStore.GetIPropertyStore()
in Vanara.Windows.Shell.PropertyStore.Run[T](Func`2 action)
in Vanara.Windows.Shell.PropertyStore.get_Keys()
in FilesFullTrust.Program.Main(String[] args) in C:\Users\Marco\source\repos\files-uwp\Files.Launcher\Program.cs:riga 49

Research
The following code works instead:
var si = new ShellItem(@"C:\ANY_FILE_PATH");
string fileSize = GetFileStringProperty(si, Vanara.PInvoke.Ole32.PROPERTYKEY.System.ItemName);
....

private static string GetFileStringProperty(ShellItem folderItem, Vanara.PInvoke.Ole32.PROPERTYKEY propertyKey)
{
    var ps = ((Vanara.PInvoke.Shell32.IShellItem2)folderItem.IShellItem).GetPropertyStore(Vanara.PInvoke.PropSys.GETPROPERTYSTOREFLAGS.GPS_DEFAULT, typeof(Vanara.PInvoke.PropSys.IPropertyStore).GUID);
    var pv = new Vanara.PInvoke.Ole32.PROPVARIANT();
    ps.GetValue(propertyKey, pv);
     var pdesc = PropertyDescription.Create(propertyKey);
     var pvalue = pdesc?.FormatForDisplay(pv, Vanara.PInvoke.PropSys.PROPDESC_FORMAT_FLAGS.PDFF_DEFAULT);
     pdesc?.Dispose();
     pv.Dispose();
     Marshal.ReleaseComObject(ps);
     return pvalue;
}

You can enumerate all valid properties using the Properties.Keys property. When I queried against a Word document, "System.Size" wasn't one of the properties.

I updated the first post. Should have described the issue better, thanks for looking into this

I also just tested and "System.Size" works as a R/O store property. After some reading, it appears that the R/O and R/W stores are actually two different streams. If you allow for inheritance, then there are multiple streams. Any thoughts on how to make this simpler to use?

I've tried your suggestion and works perfectly, thanks.
As for your question.. I'm not sure. I admit I just found out about the existence of R/W and R/O stores.
Perhaps you could make ReadOnly = true the default? If you want to write a property to the store you will have to explicitly set ReadOnly = false, then the library will try to open the R/W store and fail with a descriptive error if no R/W stores exist.

Yes, items can have an unlimited number of stores based on inheritance of containers. Most files just have one or two (R/O, R/W). I was trying to hide that complexity in my implementation, but obviously failed.

I'll post here if I decide to change the implementation model.

A more descriptive reason for failure would surely be of help in any case :)
Btw what is the correct way of disposing of the property store? And in general am I supposed to dispose of ShellFolder items returned when enumerating the contents of a ShellFolder?
var recycler = new ShellFolder(Vanara.PInvoke.Shell32.KNOWNFOLDERID.FOLDERID_RecycleBinFolder);
foreach (var folderItem in recycler)
{
	try
	{
		folderItem.Properties.ReadOnly = true;
		folderItem.Properties.NoInheritedProperties = false;
		string fileSize = folderItem.Properties.GetPropertyString(Vanara.PInvoke.Ole32.PROPERTYKEY.System.Size);
	}
	catch (System.IO.FileNotFoundException)
	{
		// Happens if files are being deleted
	}
	finally
	{
		folderItem?.Properties?.Dispose(); -----> should I do this?
		folderItem?.Dispose(); -----> should I do this?
	}
}

If I don't dispose and try to delete the item from Explorer the file delete dialog will hang until I close the program. Sorry for the dumb question.

Yes for folderItem and no for folderItem.Properties since this is done automatically by folderItem's disposal.

So I did a few things to fix/compensate on your original issue submissions:

Added improved exception (InvalidOperationException) when IPropertyStore instance cannot be created due to a shell item with no r/w support.
Changed default behavior of ShellItem.Properties so that it is read-only. It was failing for all shell items that didn't have their own properties. To get previous behavior, simply set "shellItem.Properties.ReadOnly = false" before setting properties.
Added notes to ShellItem.Properties to explain how to use.


feat: Implement AsyncPipeline

Related Issues

soft-dependency on https://github.com/deepset-ai/haystack/pull/8279

Proposed Changes:

Introduces the AsyncPipeline class that supports async Python runtimes. Uses the same execution logic as a regular Pipeline with the following changes:

The run method of the AsyncPipeline returns an asynchronous generator that yields the outputs of executed components immediately after they are run.

This allows for the streaming of intermediate results in an async environment, e.g: a RAG pipeline can yield the results of the retriever before the generator is run.
The last output yielded by the run method is the pipeline's final output.
Since method is a generator, the execution of the pipeline can only progress if its outputs are consumed. Turning that around, it allows the user to determine - after each component is executed - if the pipeline should continue running.

Components that implement an async_run method will be executed concurrently.
Components that do not implement an async_run method will be launched on a thread pool and waited on until they return a result.

In following PRs, we'll introduce variants of components that benefit from async support, i.e., I/O-bound components, primarily generators and document stores (and their associated components).
How did you test it?

Unit tests
Notes for the reviewer

The files under test/core/pipeline/features can be ignored as they've been directly lifted from the core package.
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.
I documented my code
I ran pre-commit hooks and fixed any issue

Test failures are unrelated.

Blocked from merging until haystack-experimental 0.2.0's release.


update-package-version-to-2.3.4

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary

Screenshots

Related Issue

Other

Updating to 2.3.5 next


snowflake_role should be defined as dataand not only resource

Is your feature request related to a problem? Please describe.
Yet, this is not possible to define a snowflake_role as data, so we cannot define existing role such as SYSADMIN. This can be useful to grant parent role of new role to an existing role.
The goal is to be able to do something like that:
resource "snowflake_role_grants" "grants_sysadmin_loader" {
  role_name = "${snowflake_role.loader.name}"

  roles = [
    "${data.snowflake_role.sysadmin.name}",
  ]
}

Describe the solution you'd like
Be able to define snowflake_role as data and not only resource. So instead of that (this will not work because SYSADMIN already exists):
resource "snowflake_role" "sysadmin" {
  name = "SYSADMIN"
}

We should be able to do that:
data "snowflake_role" "sysadmin" {
  name = "SYSADMIN"
}

You can import existing roles into a resource.

Hi @fonsecalink, thanks for you response.
Can you explain a bit more how to do it automatically using .tf files? Import is a cli command no?

@fonsecalink Thanks it works !

Reopening this issue. Import is working fine, but then when doing the destroy, it will try to remove the SYSADMIN role, which is not possible.

What are you trying to destroy that removes the SYSADMIN role?

@alldoami the whole workspace. terraform destroy. This is not a big problem, because except the error message in the console, the process succeeds at the end. So that's fine, but it would be better to be able to use data instead of import. Because import will then manage the resource, which we don't want for the SYSADMIN role, because it is a base role on snowflake that should not change.

Yes, that is a workaround. You can attach a prevent_destroy

@fonsecalink I want to destroy everything except this snowflake role which is a default role. The prevent_destroy stuff will just rejected the destroy, but will not do what I want to do (which is destroy everything on terraform destroy except the SYSADMIN role on snowflake)

@fonsecalink Using prevent_destroy or hitting the error @solak647 mentioned is an issue if the destroy on the workspace happens to try and destroy snowflake first. This is because in either scenario it causes the process to exit and will leave any resources that would have been destroyed afterwards behind. The only way round this is to remove the imported SYSADMIN from state prior to running the destroy.

We are closing this issue as part of a cleanup described in announcement. If you believe that the issue is still valid in v0.89.0, please open a new ticket.


I made a pleasant and understandable README.md

🎁 The fact is that the main repository still does not have a detailed installation guide. I made it.

Make it look prettier, use a markdown linter or something

🎉 I updated the README.md again
🔻 I simplified the README.md;
🔻 Emojis added;
🔻 Added badges;
🔻 I moved the finished dictionary(pass.lst) to the databases folder.

Great job!


Resilience4j not work when set 【gateway.discovery.locator.enabled=true】

when I enabled  [gateway.discovery.locator] , then resilience4j will not work. When I do not set  [gateway.discovery.locator] ,then resilience4j can work
spring cloud starter gateway version: 3.1.4
resilience4j version: 2.1.5
    gateway:
      discovery:
        locator:
          enabled: true
          route-id-prefix: /
      routes:
        - id: demo1
          uri: http://localhost:8081/
          predicates:
            - Path=/demo1/**
          filters:
            - StripPrefix=1
            - name: CircuitBreaker
              args:
                name: gmapCircuitBreaker
                fallbackUri: forward:/fallback

resilience4j.circuitbreaker:
  configs:
    default:
      failureRateThreshold: 60
      slowCallDurationThreshold: 1s
      slowCallRateThreshold: 50
      permittedNumberOfCallsInHalfOpenState: 5
      maxWaitDurationInHalfOpenState: 30s
      slidingWindowType: TIME_BASED
      slidingWindowSize: 10
      minimumNumberOfCalls: 5
      automaticTransitionFromOpenToHalfOpenEnabled: false
      waitDurationInOpenState: 10s
  instances:
    gmapCircuitBreaker:
      slowCallDurationThreshold: 1s

What do you set gateway.discovery.locator when your route doesn't use the loadbalancer?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Error marshalling JSON when Panic() is called and JSONFormatter used

I'm using JSONFormatter and calling logrus.Panic("panic msg") which gives me this error:
Failed to obtain reader, Failed to marshal fields to JSON, json: unsupported type: logrus.exitFunc
If I add a Marshaler interface for logrus.extFunc that just returns "", it works, but this involves modifying logrus vendor code. This seems related to  #835 and #642.
I don't really care about handling type-functions as field values in general--I just want to be able to call Panic()--this seems like a bug, but I fully admit I could be missing something and doing something wrong.

Hello @deusnefum, I can't reproduce the issue by just instantiating a logger with a JSONFormatter and calling Panic.
Can you provide a minimum code sample which exhibits the issue ?

I was correct that I was missing something and doing something wrong. We have generic crash-recovery code and part of that code adds the error object as a field--I think my answer is to just remove the offending field.
	if x := recover(); x != nil {
		delete(x, "Loggger")  // "fix" the problem
		// recovering from a panic; x contains whatever was passed to panic()
		logrus.WithFields(logrus.Fields{
			"error": x,
		}).Info("panic occurred")

I'll close the issue, but is there a more generic solution? Anyway to add a JSON marshaller or tell logrus to skip fields it can't marshall?


When enable use-server-properties-name server can't start.

https://pastebin.com/1GEaDQQ1
use-server-properties-name: true
Version paper 1.14.4

The server name was removed somewhere around 1.13 and 1.14, making the setting in the server.properties useless and redundant... And as you may expect does it also cause those errors when a plugin tries to load the settings while they aren't supported anymore.
Disable the setting and set an own server name in the LP config (first option)


if i just omit the suffix of python file, the editor won't recognize the file correctly

when edit the source file, like example.py it work well, but when i rename the name to example with no suffix but the grammar is python, the editor with no highlight color. atom and vim plugin works well.

it seems the editor use the lexer to decide the file type:
        return BufferControl(lexer=DocumentLexer(editor_buffer),
                             input_processors=input_processors,
                             highlighters=highlighters,
                             buffer_name=buffer_name,
                             preview_search=preview_search,
                             wrap_lines=wrap_lines,
                             focus_on_click=True)

lexer.py

    def get_tokens(self, cli, text):
        """
        Call the lexer and return the tokens.
        """
        location = self.editor_buffer.location

        if location:
            # Create an instance of the correct lexer class.
            try:
                lexer = get_lexer_for_filename(location, stripnl=False, stripall=False, ensurenl=False)
            except ClassNotFound:
                pass
            else:
                return lexer.get_tokens(text)

        return [(Token, text)]

how to change the lexer dynamically with key binding? anyone who can help me ?


Add codecov to config.yml

Codecov Report

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

@@           Coverage Diff            @@
##             master    #275   +/-   ##
========================================
  Coverage          ?   87.2%
========================================
  Files             ?      85
  Lines             ?    5206
  Branches          ?     828
========================================
  Hits              ?    4540
  Misses            ?     502
  Partials          ?     164

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0e7299...9027a1d. Read the comment docs.

@ukanga Please review

@shobhitagarwal1612 I think I was excited about this and got it merged already. Can you add the codecov badge to the readme and create a new PR, please?

Sure :+1:


improvement: Add the created address as output

This would be useful for automatically creating an A record to point to this instance

This PR is included in version 2.4.0 :tada:


Remove "mbedtls/" prefix in include file path

Status
READY
Additional comments
Fix for file not found, which was reporting in header files. In header files at mbedlts/include folder, The include path has prefix  "mbedtls/" may cause the header file not be found in the case of  mbedtls as a dynamic/static library.
Todos

[X] Tests
[ ] Documentation
[X] Changelog updated
[ ] Backported

@amisare Thank you for your interest in Mbed TLS!
We are currently in the process of CLA acceptance, therefore labeling this PR as "CLA requested".
Note: this is related to #921 which was merged before these new includes were added, and to #857

@RonEld - I can fix the ChangeLog in merge. If you see nothing else as wrong, can you please approve? Thanks.

Needs backporting, but the same PR can be used on branch 2.16.


configure script doesn't work if python3 doesn't exist

I have the perfect laptop to test this configure script with!  It's brand new with nothing on it!
Currently, with no python3 installed, I get an error when trying to run the script.

Default installs of python on even the newest Macs are python 2.7.

I like the idea of portability.  Most systems have some version of python installed, but we need to make this script support python 2 and 3.

Default installs of python on even the newest Macs are python 2.7.

It's such a shame @ Apple 😀
I was well aware of this fact, but I still chose to take a shortcut by making the script Python 3 compatible only :)

Most systems have some version of python installed, but we need to make this script support python 2 and 3.

I concur

Also, Macs don't ship with wget (only curl) which is used (by default) to download the Miniconda installer

We also need to update the CircleCI scripts to not use a base python3 container.  Rather, to use a base container that represents the default environment of someone who hasn't installed anything.
And we should create build jobs for linux (SUSE linux to mimic Cheyenne) and Mac and Windows.

BTW, I'm working on an update for Mac OS.  I'll submit a PR shortly.

And we should create build jobs for linux (SUSE linux to mimic Cheyenne) and Mac and Windows.

I am afraid we won't be able to test it on Mac on Windows via CircleCI. Per CircleCI documentation, you need to have a subscription to a paid plan: https://circleci.com/docs/2.0/hello-world-macos/#prerequisites

Ah.  I was afraid of that.

And we should create build jobs for linux (SUSE linux to mimic Cheyenne)

Since conda is OS-agnostic, and all we need is wget, and python3 from the system, do we need to do this?

Are there any functionality that is SUSE linux specific that we should be testing against?

...Well, conda is supposed to be OS-agnostic.  Can we trust that it actually is?
As for SLES specific functionality, I don't know.  Maybe not, and we can test with the same linux docker image but with different login shells.

We could move to Travis which now supports both MacOS and Windows.

Can we trust that it actually is?

Yes, we can :)

same linux docker image but with different login shells.

Testing against different login shells (bash, tcsh) seems crucial.
Regarding Windows support, looking back at our last hackathon in June, I didn't see any single windows user. Should we focus on getting this to work on windows at the moment?

Supporting windows would be worth the effort when there's actual demand IMHO :)

We had Windows users at the ACOM Python tutorial, but I haven't seen any since.

And, frankly, the word could be spreading from early Windows users that if you have a Windows machine, it's not worth it.  I'd like to make sure that isn't an issue.


administratives.json to provinces.json

Is your feature request related to a problem? Please describe.
It's confusing to retrieve provinces in administratives.json
Describe the solution you'd like
I think that it will be more efficient to rename administratives.json to provinces.json and remove the administratives key inside the json
Describe alternatives you've considered
An additional way will be to add that files aside the older one (provinces.json and administratives.json)

That a good point, your PR is welcomed

@ljoboy any update on this ?

It's done


Manually grant camera permissions

Hi there,
I am running this sample, but I had to manually grant the camera permission as I was getting the "No Permission" error on DoorbellActivity.
adb shell pm grant com.example.androidthings.doorbell android.permission.CAMERA
Do you perhaps know why permission was not granted at install time? After granting the permission the sample worked for me.

You have to reboot the device after installing the app. This is a known issue with Developer Preview 1. From the release notes:

Dangerous permissions requested by apps are not granted until the next device reboot. This includes new app installs and new  elements in existing apps.

Thanks for the information! 👍


Ensure that niced domains always span ticks

fixes #209

Now the question is there any situation we aren’t anticipating that will go into an infinite loop. :)

import {halts} from ‘halting-problem’:
Or instead perhaps a reasonable maxiter value?

We could attempt to prove that this specific code will always halt but better be safe. I added a commit to limit the number of iterations with maxiter as @jheer suggested.

I think my preference is be to prove that it will always halt, but that requires more mental effort. :)

Ideally, we would prove it for all future versions of the code as well.
Anyway, I'm happy with the code. Anything you want me to change?

Everyone please be considerate. The maxiter suggestion is designed to make sure eslint feels consulted and content.

@mbostock I'm happy with the code. Is there anything you want me to change?

@mbostock could you include this patch in a release?

I went back to var and will send a separate pull request switching to let/const.

Nice! Related https://github.com/d3/d3-array/issues/153#issuecomment-644193932

I sent https://github.com/d3/d3-scale/pull/212

Anything else you want me to change @mbostock @curran?

Anything else you want me to change @mbostock @curran @Fil?

Thanks for the reviews @curran and @Fil. @mbostock can you include this fix in a release?

ping @curran @Fil @mbostock

yes I think so—we're currently preparing a rather big release (ie d3v6)

🎉  Awesome. Looking forward to it.


sass variables not working when using color attribute for ion-tabs

Resources:
Before submitting an issue, please consult our troubleshooting guide (http://ionicframework.com/docs/troubleshooting/) and developer resources (http://ionicframework.com/docs/developer-resources/)
Please make sure you are posting an issue pertaining to the Ionic Framework. If you are having an issue with the Ionic Pro services (Ionic View, Ionic Deploy, etc.) please consult the Ionic Pro support portal (http://support.ionicjs.com)
Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
[ ] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
Please do not submit support requests or "How to" questions here. Instead, please use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Setting sass variables, such as $tabs-ios-tab-text-color, $tabs-ios-tab-text-color-active, $tabs-md-tab-text-color, $tabs-md-tab-text-color-active in /theme/variables.scss file are not being used if "color" attribute is used when declaring .
Expected behavior:

CSS style should consider sass variables declared in /theme/variables.scss file when using color attribute with
Steps to reproduce:

<ion-tabs color="secondary"> <ion-tab [root]="HomePage"></ion-tab> <ion-tab [root]="NewsPage"></ion-tab> <ion-tabs>
in /theme/variables.scss:
$colors: (
primary: #212121,
secondary: #b8d63c
);
$tabs-ios-tab-text-color: color($colors, primary);
$tabs-ios-tab-text-color-active: color($colors, primary);
$tabs-md-tab-text-color: color($colors, primary);
$tabs-md-tab-text-color-active: color($colors, primary);

Related code:

insert short code snippets here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
cli packages: (/usr/local/lib/node_modules)

    @ionic/cli-utils  : 1.12.0
    ionic (Ionic CLI) : 3.12.0

global packages:

    cordova (Cordova CLI) : 7.0.1

local packages:

    @ionic/app-scripts : 2.1.4
    Cordova Platforms  : android 6.2.3 ios 4.4.0
    Ionic Framework    : ionic-angular 3.6.1

System:

    ios-deploy : 1.9.0
    ios-sim    : 6.1.1
    Node       : v6.11.3
    npm        : 5.3.0
    OS         : macOS Sierra
    Xcode      : Xcode 9.0 Build version 9A235

Misc:

    backend : legacy

Thanks for the issue! This is the expected behavior. Styling the sass variables for the tabs only modifies the default tabs. If you add a color to the tabs then it performs some operations to determine what the text color should be.
If you're looking to override the text color for secondary, you can do something like this:
$colors: (
  primary:    #212121,
  secondary:  (
    base: #b8d63c,
    contrast: #212121
  )
);

Thanks Brandy, this works. Just a hint: maybe this spec should be made ( more? ) visible in the documentation as I couldn't find it. Regards!

@xyboox We have a section on it in Theming here: http://ionicframework.com/docs/theming/theming-your-app/
We're always interested in ways to improve though if you have any ideas. 🙂


[EN DateTimeV2] "Later in the year" should be recognized as Q3/Q4 of this year

Later in the year, Later this year should be recognized as someone in the 3rd of 4th quarter of this year.

We don't think this should be the general behaviour. Other users may have a different interpretation of "later in the year".
A more general solution that allows devs to choose how to interpret it would be to still tag year, and annotate the entity with a modifier for "later".
Similar to what happens in mid-week. @yaronism, would that work for you?

Agree. Is it supported now as we are working through LUIS.ai?


How to set a default value as an observable

I have ngrx-forms set up as per the documentation and can of course set an initial value like this:
export const initialState: FormGroupState<TermsFormState> = createFormGroupState<TermsFormState>(FORM_ID, {
  terms: 'Initial value'
});

However, the initial value is currently an observable, what is the best way to assign this value as the initial value? I was thinking using soemthing like this:
    this.formState$ = this.store.pipe(
      select(fromForms.getTermsForm),
      withLatestFrom(fromDefaults.getDefaults),
      map(([formState, defaults]) => {
        if (formState.isUntouched) {
          formState.controls.terms.setValue(defaults.terms);
        }
        return formState;
      })
    );

But it seems a little clunky just to set default values and also isUntouched always returns true

Might be useful:
https://github.com/MrWolfZ/ngrx-forms/issues/45#issuecomment-364657428
https://github.com/MrWolfZ/ngrx-forms/issues/112

Implemented a variation of the methods above, setting default state with a new action


emacs: link libXcursor when using lucid toolkit

Motivation for this change
(The implementation is) as ugly as it gets but the cursors are pretty. See https://github.com/NixOS/nixpkgs/pull/51609.
/cc @benley
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

{ toolkit = "lucid" } is broken in e.g. yesterday's unstable 29abf698b384258b540e39a86b53ea980495ac4c on Linux
the issue seems to be that patchelf is trying to patch the wrapper instead of the elf, and errors out with "patchelf: not an ELF executable"
i don't understand it enough to fix it properly other than adding another hack to make it point to the renamed ELF (why is this suddenly a problem? where does the wrapping actually happen?)
removing the patchelf hack makes it compile again without the Xcursor lib linked in, see:
https://github.com/zwizwa/nixpkgs/commit/9c92b3504bae26aa18102df8ba8d5e6695e7161e


Upgrade 'kube-dns' to 1.14.4.

According to upstream.
This also fixes #237, as I've removed the DNS_UPSTREAM_SERVERS param.

Updated the issue description in order to replace "closes" with "fixes", since one can close an issue without fixing.

I'm trusting you tested your changes - not by having kube-dns running but also doing DNS queries.

@pires I did some digging... 🙂


Enable Indexers to assign graph-node deployment rules to initial subgraph deployments

Give control of initial deployments to graph-node's deployment rules
Qualify of life request from Vincent T. | Data Nexus during IOH

Resolved in https://github.com/graphprotocol/indexer/pull/868


Add SVG Map Picker Interface extension

Hey @dimitrov-adrian, it is ok for you to link your extension here? 😃 Thanks!

Of course yes


Network in allocated state - VLAN isoltation

ISSUE TYPE

Bug Report

COMPONENT NAME

Physical Network/Guest Network

CLOUDSTACK VERSION
CloudStack <IP_ADDRESS>
CONFIGURATION
Advanced networking in use. The VPC created successfully. The assigned public IP (source-NAT) show allocated state, when try to add network it created also in allocated state.
L2 Networks with offering :2 VLANs (Manual add vlan) created with success (setup mode)
Under the physical networks public and guest vlan used as separate physical adapter and isolation method VLAN in use, VLAN range appear in the physical network.
From the management server log i found below information:
Refusing to design this network, the physical isolation type is not BCF_SEGMENT
OS / ENVIRONMENT
Virtualization Host KVM - CentOS 7 - bridge interfaces used

@jaghabalayev somewhere somehow the system is expecting BigSwitch isolation. Can you check your setup and add more infromation if needed?

@jaghabalayev
this is not a bug.
if you search 'Refusing to design this network' in the log, you will see more like
# grep 'Refusing to design this network' /var/log/cloudstack/management/management-server.log
2023-01-20 07:41:00,721 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
2023-01-20 07:41:00,722 DEBUG [o.a.c.n.c.m.ContrailGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,723 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,729 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,764 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,773 INFO  [c.c.n.g.DirectNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,777 INFO  [c.c.n.g.DirectNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network
2023-01-20 07:41:00,823 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (qtp9190301-21:ctx-3be16032 ctx-b87f6814) (logid:51c53b0d) Refusing to design this network

@weizhouapache
i have the exact error on my logs. On the network offering i didn't use BigSw services and BigSw services disabled.
I tried with Linux bridge and with OVS - the result is the same. It is my first Cloudstack installation, sorry for any incorrect information. If this not a bug, could you please provide little bit more information how can i create networks ?
The logs in my case look like:
"name": "admin", "uuid": "923dd6d0-90c5-11ed-8d55-000c29ae2b73"} to [Network Offering [23-Guest-PoCNetworkOffering-1] by AffinityGroupAccessChecker
2023-01-20 11:09:51,250 DEBUG [c.c.n.v.VpcManagerImpl] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Releasing lock for [VPC [4-PoC-11]
2023-01-20 11:09:51,285 DEBUG [c.c.n.g.BigSwitchBcfGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network, the physical isolation type is not BCF_SEGMENT
2023-01-20 11:09:51,289 DEBUG [o.a.c.n.c.m.ContrailGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,292 DEBUG [c.c.n.g.NiciraNvpGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,295 DEBUG [o.a.c.n.o.OpendaylightGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,299 DEBUG [c.c.n.g.OvsGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,303 INFO  [c.c.n.g.DirectNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,308 DEBUG [c.c.n.g.DirectNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) GRE: VLAN
2023-01-20 11:09:51,308 DEBUG [c.c.n.g.DirectNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) GRE: VXLAN
2023-01-20 11:09:51,308 INFO  [c.c.n.g.DirectNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,353 DEBUG [o.a.c.n.g.SspGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) SSP not configured to be active
2023-01-20 11:09:51,356 DEBUG [c.c.n.g.BrocadeVcsGuestNetworkGuru] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Refusing to design this network
2023-01-20 11:09:51,360 DEBUG [o.a.c.e.o.NetworkOrchestrator] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Releasing lock for Acct[923dd6d0-90c5-11ed-8d55-000c29ae2b73-admin] -- Account {"id": 2, "name": "admin", "uuid": "923dd6d0-90c5-11ed-8d55-000c29ae2b73"}

@jaghabalayev
I cannot find any clue from your management server log.
From what I get in the description, it looks like a UI bug which causes vlan range to be lost when you create the zone. The UI bug has been fixed by https://github.com/apache/cloudstack/pull/6895
can you please go to the physical networks and check if vlan range is empty ? If yes, you need to update the physical network with a vlan range. If not, can you please upload the full log ?

Hello @weizhouapache
I have already check vlan range under physical network. and it specified there. i will upload the full logs

I can see the vlan range under detail tab, however can not see the vlan range in the list of physical networks.
Is it normal behaviour ?

management-logs.zip
@weizhouapache
The log file was attached

screenshoot.zip
Screenshoots from physical network menu added

@jaghabalayev
I had a quick check on your logs
You have created multiple network offering for testing. These error seem to be caused by the new created network offering
2023-01-20 10:59:54,655 INFO  [c.c.a.ApiServer] (qtp1750498848-20:ctx-ce91bf25 ctx-087bfc02) (logid:7395e1a3) Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC [3-PoC-4]

2023-01-20 11:02:32,861 INFO  [c.c.a.ApiServer] (qtp1750498848-19:ctx-e39130d0 ctx-59297ccb) (logid:4c8302da) Vlan has to be specified; corresponding offering says specifyVlan=true

2023-01-20 11:03:08,151 INFO  [c.c.a.ApiServer] (qtp1750498848-22:ctx-b82299fc ctx-dd6d38d8) (logid:b1d23c82) Network cidr <IP_ADDRESS>/24 is not within vpc [VPC [2-PoC-VPC-GLOBAL] cidr

2023-01-20 11:03:44,095 INFO  [c.c.a.ApiServer] (qtp1750498848-412:ctx-47e20858 ctx-3b5e1bee) (logid:ced3123c) Vlan has to be specified; corresponding offering says specifyVlan=true

2023-01-20 11:24:08,485 INFO  [c.c.a.ApiServer] (qtp1750498848-20:ctx-e6869a22 ctx-d8aad01f) (logid:9589158c) Service/provider combination Lb/VpcVirtualRouter is not supported by VPC [VPC [5-PoC-New]

2023-01-20 11:31:11,940 INFO  [c.c.a.ApiServer] (qtp1750498848-19:ctx-e11fc791 ctx-af6d7f55) (logid:f72ba405) More than one physical networks exist in zone id=1 and no tags are specified in order to make a choice

2023-01-20 11:32:19,677 ERROR [c.c.a.ApiServer] (qtp1750498848-17:ctx-ed35b8a9 ctx-6a0ad51d) (logid:42b75c2e) unhandled exception executing api command: [Ljava.lang.String;@771a8053
com.cloud.exception.UnsupportedServiceException: Provider Ovs is either not enabled or doesn't support service Connectivity in physical network id=202

2023-01-20 11:33:17,509 ERROR [c.c.a.ApiServer] (qtp1750498848-16:ctx-820a4651 ctx-06fb4dba) (logid:65f2a9f5) unhandled exception executing api command: [Ljava.lang.String;@3b371888
com.cloud.exception.UnsupportedServiceException: Provider VpcVirtualRouter is either not enabled or doesn't support service Dhcp in physical network id=202

2023-01-20 11:34:58,195 ERROR [c.c.a.ApiServer] (qtp1750498848-19:ctx-2724bf6d ctx-6a805c8d) (logid:ac52a8ce) unhandled exception executing api command: [Ljava.lang.String;@295500ac
com.cloud.exception.UnsupportedServiceException: Provider VpcVirtualRouter is either not enabled or doesn't support service Dhcp in physical network id=202

some networks have been created successfully
2023-01-20 10:54:33,664 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp1750498848-21:ctx-554b62c6 ctx-fe5bdbd8) (logid:b25c28fd) Updating resource Type = network count for Account = 2 Operation = increasing Amount = 1

2023-01-20 11:09:51,367 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp1750498848-17:ctx-9841c0fe ctx-82941bca) (logid:a9e3faa6) Updating resource Type = network count for Account = 2 Operation = increasing Amount = 1

2023-01-20 11:26:04,085 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp1750498848-403:ctx-1e2fa873 ctx-0f1d6863) (logid:9c95e1f6) Updating resource Type = network count for Account = 2 Operation = increasing Amount = 1

2023-01-20 11:51:13,474 DEBUG [c.c.r.ResourceLimitManagerImpl] (qtp1750498848-412:ctx-7d124df9 ctx-32c95c2a) (logid:9fcaf791) Updating resource Type = network count for Account = 2 Operation = increasing Amount = 1

I did not see anything wrong.
can you use the default offering DefaultIsolatedNetworkOfferingForVpcNetworks to create vpc tiers ?

@weizhouapache
DefaultIsolatedNetworkOfferingForVpcNetworks - i used this offering also, the result is same.
The network created successfully, but in allocated state. When i add network with VLAN ID manually it created with success.
Looks like management server couldn't fetch the information from VLAN pool for guest networks

@jaghabalayev
Allocated state is the right state for new isolated networks. When you create or start a vm in the network, the network will be implemented (including fetch a free VLAN id from the VLAN range) and changed to Implementing->Implemented state.
When there is no vm running, cloudstack will shutdown the network and free the vlan after a period.
If you create a network offering with Persistent = true, the network created with the network offering will be implemented soon after you create it.
Depends on your requirement, you can create network offerings with different settings.

@weizhouapache
I tried to created VM and use the created network (allocated), but VM creation failed with error - couldn't assign network in allocated mode

@weizhouapache I tried to created VM and use the created network (allocated), but VM creation failed with error - couldn't assign network in allocated mode

@jaghabalayev
any logs ?

@weizhouapache
for now i install from scratch Management Server and KVM node - and it works fine.
However what i noticed that during changing confugration over GUI physical networks and VLAN range the Database not updated. Old rows still remaning in the DB. I attached screen before reinstalling appliance and it shows old networks and VLAN which have already been deleted.
So the DB is not updated during deleting VLAN pools from physical networks
![db-not-updated](https://user-images.githubusercontent.com/66360297/213809039-5685edda-0d97-47c0-926d-16f706

056ecc.jpg)

@weizhouapache for now i install from scratch Management Server and KVM node - and it works fine. However what i noticed that during changing confugration over GUI physical networks and VLAN range the Database not updated. Old rows still remaning in the DB. I attached screen before reinstalling appliance and it shows old networks and VLAN which have already been deleted. So the DB is not updated during deleting VLAN pools from physical networks ![db-not-updated](https://user-images.githubusercontent.com/66360297/213809039-5685edda-0d97-47c0-926d-16f706  056ecc.jpg)

@jaghabalayev
in some database tables which have the 'removed' column, the records are not deleted, cloudstack just updates the 'removed' to the datetime when the resource becomes unavailable.

Thank you for information @weizhouapache


The Training result is higher than the test?

Hello, when I trained the PSPNet50 on the cityscapes dataset, I get 0.8266 miou in the training after 200 epochs, and 0.7764 miou in the test, and 0.6971 miou in the valuation. My environment is pytorch 1.6, 8 Tesla V100 GPUs. Thanks!

Have you solved it? I'm facing the same situation here.

The evluation in train.py gives different result compare to test.py. I don't understand why

The evluation in train.py gives different result compare to test.py. I don't understand why

I meet the same question.

The evluation in train.py gives different result compare to test.py. I don't understand why

I meet the same question.

For some unknow reason author decided to f * k up everybody demostating better result than they really are. In test inference is launched per patches and than combined together. So results will be higher basically because input reolution is higher, and he doesn't give a s * t that this way has very poor performance (could be significant for many applications)

The evluation in train.py gives different result compare to test.py. I don't understand why

I meet the same question.

Test. For some unknow reason author decided to f __k up everybody demostating better result than they really are. In test inference is launched per patches and than combined together. So results on standart datasets are higher on test, Nad he doesn't give a s__t on perfomance.
2)Train. For some unknow reason author decided to add random crop (instead resize) to transformations in dataset though it can dramatically change results for many applications.
Such is it vanity of github contributors and we need to use their code because have tasks on our bad jobs when we aren't provided with enough time to write it from scratch

The evluation in train.py gives different result compare to test.py. I don't understand why

I meet the same question.

Test. For some unknow reason author decided to f __k up everybody demostating better result than they really are. In test inference is launched per patches and than combined together. So results on standart datasets are higher than in other implementation, and he doesn't give a s__t on perfomance.
Train. For some unknow reason author decided to add random crop (instead resize) to transformations in dataset though it can dramatically change results for many applications.

Such is it vanity of github contributors and we need to use their code because have tasks on our bad jobs when we aren't provided with enough time to write it from scratch

I have solved this problem.  There is an error in the saving path of the picture in test.py. You should modify it in your own code.
I change 'image_name = image_path.split('/')[-1].split('.')[0]' to 'image_name = image_path.split('/')[-1][:-4]'  in test function and cal_acc  function. After my modification,  I find the calculation result is right.

与 test.py 相比，train.py 中的评估给出了不同的结果。我不明白为什么

我遇到了同样的问题。

测试。由于某种未知的原因，作者决定让每个人都比他们实际的结果更好。在测试中，推理是按补丁启动的，然后组合在一起。因此，标准数据集的结果高于其他实现，而且他没有给出性能方面的评价。
火车。由于一些未知的原因，作者决定在数据集中的转换中添加随机裁剪（而不是调整大小），尽管它可以显着改变许多应用程序的结果。

这就是 github 贡献者的虚荣心，我们需要使用他们的代码，因为当我们没有足够的时间从头开始编写代码时，我们的工作很糟糕

我已经解决了这个问题。test.py中图片的保存路径有错误。您应该在自己的代码中修改它。 我将 'image_name = image_path.split('/')[-1].split('.')[0]' 更改为 'image_name = image_path.split('/')[-1][:-4]'在测试函数和 cal_acc 函数中。经过我的修改，我发现计算结果是对的。


NT-1171(Fix): Manage Pledge UI fixes

📲 What
Manage Pledge UI changes
🤔 Why
Clean up UI to closer match Figma designs
🛠 How
Make sure text colors match by using correct colors in spans, fix font sizing and string references.
👀 See

, external resources?
📋 QA
https://kickstarter.atlassian.net/secure/RapidBoard.jspa?rapidView=9&modal=detail&selectedIssue=NT-1171
Story 📖
https://kickstarter.atlassian.net/secure/RapidBoard.jspa?rapidView=9&modal=detail&selectedIssue=NT-1171

Merging this!


Discrepancy between the number of 'reported' Edge caches and the number monitored

The following api will pull the server status count directly out of the database for all EDGEs:
/api/1.2/servers/status?type=EDGE
this will include a "reported" number of edges.
This api will pull the number of online (healthy) and offline (unhealthy) Edge caches:
/api/1.2/cdns/health
The number of online (healthy) and offline (unhealthy) Edge caches should equal the number of "reported" caches. However, there seems to be a slight discrepancy.

seems to be working now...


configd: files generated from templates do not have trailing newlines

Similar issue/fix here: https://github.com/saltstack/salt/commit/bdf5d0dc01230d684b861f5bbeded992a474dd8c

Do you have an example? If the last tag is a template expression, the newline is cut on purpose. (trim_blocks, see http://jinja.pocoo.org/docs/dev/templates/ )

Noticed this before, behaviour is consistent...
root@os:~ # cat /etc/rc.conf.d/squid
squid_enable=YES
squid_opnsense_bootup_run="/usr/local/opnsense/scripts/proxy/setup.sh"root@os:~ #

Note that "trailing newlines" means "the very last newline in the template" here. Sorry for the ambiguity.

strange, same cat on my end:
root@OPNsense:~/core # cat /etc/rc.conf.d/squid
squid_enable=YES
squid_opnsense_bootup_run="/usr/local/opnsense/scripts/proxy/setup.sh"
root@OPNsense:~/core #
what does src/opnsense/service/templates/OPNsense/Proxy/rc.conf.d look like on your end? does it contain the trailing newline?

No, it has the same defect. That was my reason for submitting this today. :)

Now I'm confused.... the template is missing the end of line on your end and the output also doesn't have the line? My version does have the end of line in both.
If the end of line is not in the source, it shouldn't be in the target as well.. that's how it's supposed to work.

Sorry, I debugged using suricata file, then I mixed up the template question you had. The templates all have newlines as per cleanfile script, the actual files generated don't.

Ok, no problem. Only thing weird in here is why my install doesn't show the same behaviour. I will try the same on another box as well, maybe I can reproduce it somewhere. This shouldn't go wrong if the last tag isn't a template tag.

Fixed in https://github.com/opnsense/core/commit/d8a81cda7b0213e581fd6fe7c68231aa6fdae6d2


*: prepare Thanos for stringlabels

Some preparations to be able to build with stringlabels later. Its not complete yet but large enough; notable exception is pkg/store; but it should be tackled in a followup PR.
Inspired by prior art: #6394

Do we want a CI job to verify we can compile Thanos with the stringlabels tag?

eventually yes, but we are not there yet!


No option to Request for Code and Token or Token alone

Seems like there is no option to request for code and token together.
I'm not sure how to categorize this scenario exactly.
Previously I have used few openid plugins where I can initiate an authentication request with both code and token together. During redirection we will receive both code and token as per the response mode.
Is there any option available for this in this plugin ? If Yes please specify that.
My requirement is something like below:
<Auth0Provider         domain="DOMAIN"         clientId="CLIENT_ID"         redirectUri="URL"         response_type="code token"     ></Auth0Provider>
Basically I would like to add another option for response_type or responseType where I can pass wether I need token or code or both together.
Any help would really appreciated
Thanks in advance.

Hi @achyuthgroot - thanks for raising this
This SDK uses the code flow with PKCE only - we don;t recommend using Implicit (or in your case Hybrid) flows for SPA applications.
More info here https://auth0.com/blog/oauth2-implicit-grant-and-spa/

Hi @achyuthgroot - thanks for raising this
This SDK uses the code flow with PKCE only - we don;t recommend using Implicit (or in your case Hybrid) flows for SPA applications.
More info here https://auth0.com/blog/oauth2-implicit-grant-and-spa/

Good to hear the confirmation, it seems the documentation is not very clear about whether this package is using implicit flow or PKCE


template for jira issues/jira api fields

add a template or config file in which the user can set which fields of the jira tickets shall be written, the config file must contain information on how the data needs to be added to a jira issue on the server

Template is not needed, the tool will take a raw form of the issue, which is a dictionary, and write it to a json file. This way no configuration is neccessary. Every instance of a jira server will just write all the information available.


33 - Create the navigation elements of the design system

What this PR does / why we need it:
This PR adds the navigation elements of the design system. This is the Navbar.tsx, Breadcrumb.tsx and Tabs.tsx components.
Which issue(s) this PR closes:

Closes #33

Special notes for your reviewer:
I added the 3 navigation elements as described in the Design System Analysis following Bootstrap 5 styles. For the Navbar element since it was already developed I just did a refactor to improve readability.
Suggestions on how to test this:
npm run storybook
You can check in the Storybook the Breadcrumbs, Tabs and Navigation elements
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
None
Is there a release notes update needed for this change?:
Added navigation elements of the design system
Additional documentation:
Design System Analysis doc

I'm not sure what I should be seeing, verifying. I see a navbar item in the left hand links column. I open the docs for it and see model navbar header components: links, drop down list, but I do not see tabs?

I'm not sure what I should be seeing, verifying. I see a navbar item in the left hand links column. I open the docs for it and see model navbar header components: links, drop down list, but I do not see tabs?

When you open storybook there should be 3 elements for the navigation: the Navbar, the Tabs and the Breadcrumbs

@MellyGray Thanks! I think it was the same -b issue. I wasn't seeing the latest? Anyway, I see them now.

@MellyGray There is a merge conflict with the pr. Can you take a look?

@kcondon I fixed the conflicts now


[Broken] Roosterteeth.com Subtitles

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dlc version 2020.11.11
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Windows\system32>python3 -m pip install --upgrade youtube-dlc
Collecting youtube-dlc
  Using cached youtube_dlc-2020.11.11.post3-py2.py3-none-any.whl (1.8 MB)
Installing collected packages: youtube-dlc
Successfully installed youtube-dlc-2020.11.11.post3

C:\Windows\system32>youtube-dlc -v https://roosterteeth.com/watch/rwby-season-1-episode-1 --list-subs
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://roosterteeth.com/watch/rwby-season-1-episode-1', '--list-subs']
[debug] Loading archive file None
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dlc version 2020.11.11-3
[debug] Python version 3.7.9 (CPython) - Windows-10-10.0.19041-SP0
[debug] exe versions: ffmpeg 4.3.1, ffprobe 4.3.1
[debug] Proxy map: {}
[RoosterTeeth] rwby-season-1-episode-1: Downloading video JSON metadata
[RoosterTeeth] rwby-season-1-episode-1: Downloading m3u8 information
[RoosterTeeth] rwby-season-1-episode-1: Downloading episode JSON metadata
16024 has no subtitles

C:\Windows\system32>youtube-dlc --version
2020.11.11-3

Description

youtube-dlc does not recognize subtitles on roosterteeth.com.
Links that were tested:

https://roosterteeth.com/watch/rwby-season-1-episode-1
https://roosterteeth.com/watch/rwby-season-1-episode-2
https://roosterteeth.com/watch/rwby-season-1-episode-3
https://roosterteeth.com/watch/rwby-season-1-episode-4
https://roosterteeth.com/watch/gary-and-his-demons-season-1-still-the-one

I am able to load all the subtitles using the built-in player, so this is a youtube-dlc issue. The exact same issue is present in pukkandan's fork, and an issue has been made there as well.
A pull request is made on youtube-dl's repo here, but has not been merged for several months.

This has been fixed in youtube-dlp. I recommend merging this pull request as a possible fix. This issue still remains in this fork, so this will remain open.

This has been fixed in youtube-dlp. I recommend merging this pull request as a possible fix. This issue still remains in this fork, so this will remain open.

This repo is no longer maintained anyway. The official youtube-dlc repo is moved to https://github.com/blackjack4494/yt-dlc after the DMCA takedown.

This repo is no longer maintained anyway. The official youtube-dlc repo is moved to https://github.com/blackjack4494/yt-dlc after the DMCA takedown.


feat: add rpc.make functionality

Coverage decreased (-5.4%) to 72.917% when pulling 44f7446c5a7222caa5d735ef81614323a20df60f on add-rpc-make into 376cca50994324dbc25fd823dd23c805c7ca7f09 on master.


[Blocking] CI for R freeze

refer to https://github.com/microsoft/LightGBM/runs/955837580
It seems the installation of Rtools (with R 4.0) freezes.
ping @jameslamb

Ok I can look in 10 minutes

ok looking right now

I'm going to push changes to #3277 to test, since that is a small R change that was already approved.

😕 I tried removing /VERYSILENT so we could get more logs installing Rtools, but no luck. I don't see any other configuration options that can help here.
https://github.com/microsoft/LightGBM/pull/3277/checks?check_run_id=956113469
Telling R to use MinGW
Downloading R and Rtools
Downloading https://cloud.r-project.org/bin/windows/base/old/3.6.3/R-3.6.3-win.exe
Downloading https://cloud.r-project.org/bin/windows/Rtools/Rtools35.exe
Installing R
Done installing R
Installing Rtools
##[error]The operation was canceled.

Those logs tell us that:

R was found and could be downloaded
Rtools was found and could be downloaded
installation of R succeeds
installation of Rtools times out

Since there has not been an Rtools release since June 22, and since we're seeing this issue even on Rtools35, I have these theories:

Some service Rtools relies on (like a CTAN mirror or a package server for pacman) is down
some subtle networking thing has changed in Azure that is blocking traffic to some place Rtools wants to hit

I just looked on the pacman mirrors and I see a LOT of errors recently!!!

and other mirrors not reporting errors are way out of sync

Given this, @guolinke I think you should use your administrator privileges to merge #3071 . We don't know how long it will take for this to be resolved, and it shouldn't hold up releases for all the other non-R components any loonger.

@jameslamb thank you so much.
No problem, I will merge it first.

I just checked and the pacman repos still seem to be down. I hope it's resolved soon.

I have been trying with #3277 and I still see this issue :/
This is difficult because even after removing the /VERYSILENT, we're still not getting any logs. Going to pull out my Windows laptop and try running this code there.
It seems that a lot of the pacman mirrors are working now...maybe that was never the issue to begin with, I don't know. Maybe something in Rtools is asking for a user input and hung waiting on it.

Ok making progress!!! Now I think that the pacman thing was completely unrelated.
I found that the download code we've been using to get Rtools is returning a successful status, but not actually downloading anything!!!

and then if you run the code to install Rtools and the file doesn't exist, you get a dialog box that has to be confirmed in a GUI. That is why it's hanging in CI!!

I'm investigating how to fix this. Maybe the download link from CRAN is now redirecting and the powershell code in test_r_package_windows.ps1 isn't following that?

hmmmm doesn't seem like it's a redirect.

According to your screenshots you are downloading from cran.r-project.org, but our CI tries to download from cloud.r-project.org. Maybe this matter...
https://github.com/microsoft/LightGBM/blob/33af069cc174a4c56c5f1e2f351196a284248f80/.ci/test_r_package_windows.ps1#L105-L106
On my local machine CI code works fine and downloads both R and Rtools sucessfully.

😱 😱 😱 😱 😱

when I change to cloud, it still does not download a file on my laptop

when I switch to Invoke-WebRequest with the same URL, a file is downloaded!

I'm so confused 😕

I just switched to Invoke-WebRequest on #3277 and R Windows jobs for R 3.6 are now passing, but the ones for R 4.0 are still pending after 25 minutes :/
This is tough because you cannot (as far as I know) pin to one distribution of Rtools as long as it is not "frozen" (https://cran.r-project.org/bin/windows/Rtools/history.html).

So the Rtools.exe you get today might not be the one you get from the same link tomorrow.

I just pushed a commit to #3277 that switches from cloud. links to cran. links for R and Rtools. I also added an ls after the downloads, so we can see in the logs if the files were downloaded and that that was the issue.

ok from the logs on #3277, it seems that the files ARE getting downloaded successfully.
So something else is failing for Rtools 4.0 specifically :/

My guesses now are:

some package manager (pacman or something else) used in the install process is not responding
some weird networking issue with Azure that is preventing Rtools from completing some request
something in Rtools is popping up a user dialogue and hangs forever waiting for it to be answered

When I run this on my laptop
Start-Process -FilePath C:\Users\James\repos\sandbox\Rtools.exe -NoNewWindow -Wait -ArgumentList "/DIR=C:\Users\James\repos\sandbox"

A dialogue box pops up

oh I forgot to add /VERYSILENT above. When I do that
Start-Process -FilePath C:\Users\James\repos\sandbox\Rtools.exe -NoNewWindow -Wait -ArgumentList "/VERYSILENT /DIR=C:\Users\James\repos\sandbox\rtools"

the process just hangs forever :/

Can you please try to duplicate (escape) \ signs in DIR argument and add SUPPRESSMSGBOXES argument?
https://github.com/r-lib/actions/blob/32bf69a8dfce4486d4f2221a3a6ea9b1dd75eadb/setup-r/lib/installer.js#L270-L272

oooo sure!
I also just found that I can stop the "hangs forever" problem locally by changing the command to this:
 C:\Users\James\repos\sandbox\Rtools.exe /VERYSILENT /DIR=C:\users\James\repos\sandbox\rtools

So maybe something about the new Rtools does not work well with Start-Process on some versions of PowerShell?

hey maybe that is working?
Here is one of the R 4.0 jobs getting past Rtools (https://github.com/microsoft/LightGBM/pull/3277/checks?check_run_id=962455060)

I need to step away for a few hours, but hopefully that was it and the build on #3277 will work. @StrikerRUS please feel free to push to that PR if you want, I know that this issue is blocking everything right now. I'll be back on in about 3 hours to try other things.

this was  fixed by #3277


Changes done

🛠 Fixes Issue

Issue fixed

📷 Screenshots

Kindly look once.. please inform for any task.

Generate new merge request #100 kindly check .. Sorry for this!


us-fl-polk

Polk County, FL has data published on the web, but can't find anything with addresses. They have a GIS data downloads page published, but no license info that I can see, either.
I've reached out to their help desk and will update with more info if I hear from them.

All public data in Florida is public domain unless specifically exempted by FL Statute Chapter 119. GIS data is not exempt.
Polk county address points are available here:
<EMAIL_ADDRESS>Data/SitePoints.shp
Site is not responding at the moment, but I grabbed the data from there the other day.

Closing as stale.


feature request: use single transaction for all queries made in a connection

I am using lambdas in AWS and I had an error like this today:
Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

obviously I had a missing transaction in one of my objection.js queries, but I wondered-wouldn't it be possible to have a knexfile config like:
module.exports = {
  client: 'postgres',
  connection: {
    singleTransaction: true
  }
}

where knex would basically create a transaction and passed it around to all my queries without me having to explicitly state it for every one of them? In lambda I always want a behavior like this, because if lambda fails it is retried automatically so it's typical that I put all of my DB work in a single transaction.
Maybe my usecase is not very common, but seeing as lambdas are becoming quite common in the world of cloud computing, maybe supporting this usecase would make sense. WDYT?

You can easily implement this by creating singleton transaction instead of knex instance.
const trx = knex.transaction();

In handler use trx the same way you would use the knex instance:
 const res = await trx(’users’).where(’id’, 1);

And remember to commit when handler is ready... knex wouldn’t know when to do that anyways so with proposed functionality knex would rollback every time when connection closes unexpectedly.

oh right! :facepalm:
I could initialize my objection with
objection.Model.knex(trx)

thanks for that suggestion. That should work just fine!
Thanks. Will give this a shot.


Add Text for ComponentPrefabs

Hello,
I've just noticed that there is no single Text component in the prefab and in the MaterialUI menu.
It will be really handy to create a Label just like any other component ;)

Hey there!
Unless you wanted something specific, you can just create them

Yes of course, but as I use everything under the MaterialUI menu, it would be better if everything was at the same place, so we don't have to look in 200 menus. That's just my opining of course :)

Sure thing. I might make it default to the Roboto font while I'm at it :)

Yes forgot to tell you that, only for that it's essential :)


today,it doesn't work ,but it did work yestoday

🚨 The issue tracker is not for questions 🚨
If you have a question, please ask it on https://stackoverflow.com/questions/tagged/wechaty
[question]

Merge to

https://github.com/wechaty/puppet-wechat/issues/192


Choose RPCs from a single file

ODHack
This issue is part of ODHack:

Description
Guidelines

Description
Create a script to create ten funded accounts that will be executed when starting the project, on standalone.
Also, create a function called  getFundedAccounts to get those funded on .ts file.
Deploy script should take the accounts[0] as the admin account.
Acceptance Criteria
Accounts should be retrievable by calling the function getFundedAccounts
Note
describe the structure of files (where and with which names will be saved) in a comment to be assigned to this issue

I will add a new field called ChildAccounts in EnvConfig here which will store the newly created accounts.
I will create a new file called get_funded_accounts.ts and implement getFundedAccounts fn to retrieve all funded accounts. This function will accept EnvConfig object to extract the funded account keys and get their balances. Otherwise, when creating EnvConfig object from the configs.json, we can add each account's secret to environment, so  we can use getUser fn to get key pair and use it to retieve the balance.

GM @chopan123, here's my portfolio: https://www.jedshock.com/. I hope I am deem fit enough to tackle on this issue?


Add cansee support for sample data

Description

Sample view can now pull data from other groups.
Add tests!

Depends on #156
Test plan
All sorts of exciting combinations!

Ok I fixed this so we can do this in two DB requests instead of three.


Example of not escaping lang_doc string

We can un-escape YAML special chars by putting them in single-quotes.
By following this example, we should be able to fix pubsub_gapic.yaml and close out https://github.com/googleapis/gapic-generator/issues/937
The resulting @ literal @ is kinda weird but it's in line with the rendering in https://github.com/googleapis/gapic-generator/blob/580c79d8aecadd5f401b9a333c76af7c7f381907/src/test/java/com/google/api/codegen/gapic/testdata/java/java_library.baseline#L3918

PTAL

I think you got the issue backwards. I think we should be able to not escape. Eg, if we actually want to insert a @See This.Other.Class in the Javadoc, we should be able to.

@pongad whoops yes fixed title.
The content of the PR is not backwards tho is it?

I think it is right? It's a little confusing to explain, so let me know if you want to follow up on IM.
But imagine what you might do if you actually want to insert a link in the Javadoc. If you're editing the Javadoc directly, you might write @see the.Class. But writing that in lang_doc doesn't create a link, it writes {@literal @}see the.Class which renders @see the.Class. Am I making this more confusing? :rofl:

@pongad I am confused, yes. How is this different from
 *         {@literal @}Override

in the generated method comment?

I'm lacking context on this PR. Why do you have a PR exemplifying how not to escape?
Not an expert on javadoc, but it seems to me the output in the baselines is not what we want: we do want the {@see everywhere} just copied from the config, right? Is there a reason we cant just copy it?
Again, I'm probably missing the context/motivation for this PR.

No action on this, not sure we need it. Closing for now.
fyi: @hzyi-google


Properly add IPOPT on MacOS

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] ~Reset the build number to 0 (if the version changed)~
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Close #7

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

It looks like the 'scip' output doesn't have any tests.
It looks like the 'soplex' output doesn't have any tests.
License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender